7.5

CVE-2026-68496: fasterxml jackson-dataformats-binary Uncontrolled Resource Consumption

CVSS: 7.5v3.1HighAwaiting analysis
AliasesUBUNTU-CVE-2026-68496DEBIAN-CVE-2026-68496
Published 01-10-2026Last modified 01-10-2026

Vulnerability summary

CVE-2026-68496 is a high (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in fasterxml jackson-dataformats-binary. EPSS estimates a 0.67% chance of exploitation in the next 30 days, higher than 50.9% of scored vulnerabilities.

Overall risk
30/100
0100
Medium · default modelHow is this calculated?
CVSS score
7.5/10
010
High · v3.1 (CVE.org)
EPSS score
0.67%
0%100%
Low · Change unavailable
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 2 · Related 2

Timeline

  1. 01-10-2026
    PublishedVulnerability first disclosed.
  2. 01-10-2026
    Last modifiedVulnerability information updated.

Description

The Smile 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. SmileParser._handleLongFieldName() grows its internal name buffer through an unconstrained _growArrayTo() call and performs no length validation. An attacker who can have a Smile 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 SmileFactory parsing, directly or through an ObjectMapper configured with the Smile 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 CBOR parser defect in the same vendor advisory, GHSA-3v8f-v6vx-fmrm, which covers both binary formats. The Smile parser defect (jackson-dataformats-binary issue #726) is CVE-2026-68496; the CBOR parser defect (issue #725) is assigned CVE-2026-68495.

CVSS metrics

4 scores · 4 sources · 1 version

EPSS trend

Probability

0.67%

Chance of exploitation in the next 30 days

Percentile

51%

Versus all other CVEs

30-day change

Change unavailable

Change unavailable

02-10-202620-10-2026
EPSS score
0.67%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Debian1 product
  • jackson-dataformat-smileAll versions (No fix recorded)
Fasterxml1 product
  • jackson-dataformats-binary≥ 2.16.0, ≤ 2.18.9 | ≥ 2.19.0, ≤ 2.21.5 | ≥ 2.22.0, ≤ 2.22.1 | ≥ 3.0.0, ≤ 3.1.5 | ≥ 3.2.0, ≤ 3.2.1
Ubuntu1 product
  • jackson-dataformat-smileAll versions (No fix recorded)

3 vendors · 3 products

References

7 links