CVE.org (no NVD analysis yet)· CNA HeroDevs

CVE-2026-68495: jackson-dataformats-binary: CBOR parser does not enforce StreamReadConstraints.maxNameLength, enabling memory-exhaustion denial of service

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.56% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: jackson-dataformats-binary (openSUSE:Tumbleweed) 2.18.11-1.1; jackson-annotations (SUSE:Linux Enterprise Module for Basesystem 15 SP7) 2.18.11-150200.3.28.1; jackson-core (SUSE:Linux Enterprise Module for Basesystem 15 SP7) 2.18.11-150200.3.30.1.

Low priority for now. Upgrade to jackson-dataformats-binary (openSUSE:Tumbleweed) 2.18.11-1.1; jackson-annotations (SUSE:Linux Enterprise Module for Basesystem 15 SP7) 2.18.11-150200.3.28.1; jackson-core (SUSE:Linux Enterprise Module for Basesystem 15 SP7) 2.18.11-150200.3.30.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The CBOR parser in FasterXML jackson-dataformats-binary never invokes StreamReadConstraints.validateNameLength() when decoding JSON object property names, so the maxNameLength limit is not enforced for this format. CBORParser._decodeLongerName() decodes a definite-length property name with no length check, and CBORParser._decodeChunkedName() delegates to the value-oriented _finishChunkedText() routine, which validates maxStringLength rather than maxNameLength. An attacker who can have a CBOR document parsed may therefore embed a single property name of unbounded length; the parser buffers the whole name in memory before returning it, whatever maxNameLength is configured to. Because StreamReadConstraints.maxDocumentLength is also disabled by default, nothing else bounds the name under default settings, so the only limits are the attacker's upload capacity and available heap, leading to memory exhaustion and denial of service. No privileges beyond the ability to submit data to a parsing endpoint are required, and exploitation needs only that the bytes reach CBORFactory parsing, directly or through an ObjectMapper configured with the CBOR module. jackson-core's own JSON parsers enforce maxNameLength incrementally during name decoding; this gap is specific to the binary formats. maxNameLength and validateNameLength were introduced in jackson-core 2.16.0, so releases before 2.16.0 do not contain the constraint that is left unenforced. This issue is tracked together with the Smile parser defect in the same vendor advisory, GHSA-3v8f-v6vx-fmrm, which covers both binary formats. The CBOR parser defect (jackson-dataformats-binary issue #725) is CVE-2026-68495; the Smile parser defect (issue #726) is assigned CVE-2026-68496.

HighCVSS 7.5 · v3.1—No exploit Fix available

Published: Oct 1, 2026
Updated: Oct 2, 2026
EPSS: 0.5% · 46th percentile
CWE: CWE-400

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: proof of concept
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · HeroDevs: 7.5; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (HeroDevs). Independent of NVD's CPE analysis and usually ahead of it.

FasterXML jackson-dataformats-binary
- 2.16.0 and later · up to and including 2.18.9affected · maven
- 2.19.0 and later · up to and including 2.21.5affected · maven
- 2.22.0 and later · up to and including 2.22.1affected · maven
- 3.0.0 and later · up to and including 3.1.5affected · maven
- 3.2.0 and later · up to and including 3.2.1affected · maven

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	jackson-dataformat-cbor	from 0	—
openSUSE:Tumbleweed	jackson-dataformats-binary	before 2.18.11-1.1	2.18.11-1.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7	jackson-annotations	before 2.18.11-150200.3.28.1	2.18.11-150200.3.28.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7	jackson-core	before 2.18.11-150200.3.30.1	2.18.11-150200.3.30.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7	jackson-databind	before 2.18.11-150200.3.36.1	2.18.11-150200.3.36.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7	jackson-dataformat-xml	before 2.18.11-150200.5.8.1	2.18.11-150200.5.8.1
SUSE:Linux Enterprise Module for Development Tools 15 SP7	jackson-dataformats-binary	before 2.18.11-150200.3.29.1	2.18.11-150200.3.29.1

Same product

fasterxml: all records

Other highest-scoring records for the same primary product.

CVE-2020-28491Denial of Service (DoS)
31Monitor
CVE-2026-68496jackson-dataformats-binary: Smile parser does not enforce StreamReadConstraints.maxNameLength, enabling memory-exhaustion denial of service
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
opensuse:jackson-dataformats-binary	2.18.11-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
suse:jackson-annotations	2.18.11-150200.3.28.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7	Package registry (OSV)
suse:jackson-core	2.18.11-150200.3.30.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7	Package registry (OSV)
suse:jackson-databind	2.18.11-150200.3.36.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7	Package registry (OSV)
suse:jackson-dataformat-xml	2.18.11-150200.5.8.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7	Package registry (OSV)
suse:jackson-dataformats-binary	2.18.11-150200.3.29.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedOct 1, 2026
Fix recordedOct 2, 2026same day
TodayNov 9, 2026+39 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

tinyb0yfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-684960 days apartjackson-dataformats-binary: Smile parser does not enforce StreamReadConstraints.maxNameLength, enabling memory-exhaustion denial of service
30Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

The bug in code

The whole CWE-400 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1function expand(node) {
2  return node.children.map(expand);
3}

Fixed

1const MAX_DEPTH = 32;
2function expand(node, depth = 0) {
3  if (depth > MAX_DEPTH) throw new Error("too deep");
4  return node.children.map((c) => expand(c, depth + 1));
5}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Endpoint Denial of ServiceT1499

Change log

Fix✗ → ✓Oct 2, 2026, 3:29 AM UTC
SSVC exploitation— → pocOct 1, 2026, 9:07 PM UTC
Exploit maturity— → noneOct 1, 2026, 7:07 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/FasterXML/jackson-dataformats-binary/blob/2.18/release-notes/VERSION-2.x

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records