CVE-2026-68495 jackson-dataformats-binary: CBOR parser does not enforce StreamReadConstraints.maxNameLength, enabling memory-exhaustion denial of service
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- Proof of concept public · automatable: yes · technical impact: partial
- Technology
- UbuntuDebian
Description
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.
Upgrade path
9 packages: 2 fixed, 7 with no fix yet.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| debian/jackson-dataformat-cbor(Debian 12) | = 2.7.8-5; = 2.7.8-5.1; All versions | No fix listed | No fix yet |
| debian/jackson-dataformat-cbor(Debian 13) | = 2.7.8-5.1; All versions | No fix listed | No fix yet |
| debian/jackson-dataformat-cbor(Debian 14) | = 2.7.8-5.1; All versions | No fix listed | No fix yet |
| ubuntu/jackson-dataformat-cbor(Ubuntu 22.04) | All versions | No fix listed | No fix yet |
| ubuntu/jackson-dataformat-cbor(Ubuntu 24.04) | All versions | No fix listed | No fix yet |
| ubuntu/jackson-dataformat-cbor(Ubuntu 26.04) | All versions | No fix listed | No fix yet |
| ubuntu/jackson-dataformat-cbor(Ubuntu 26.10) | All versions | No fix listed | No fix yet |
| com.fasterxml.jackson.dataformat/jackson-dataformat-cbor(Maven) | >= 2.16.0, <= 2.18.9; >= 2.19.0, <= 2.21.5; >= 2.22.0, <= 2.22.1 | after 2.18.9, 2.21.5, 2.22.1 | Fixed |
| tools.jackson.dataformat/jackson-dataformat-cbor(Maven) | >= 3.0.0, <= 3.1.5; >= 3.2.0, <= 3.2.1 | after 3.1.5, 3.2.1 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| com.fasterxml.jackson.dataformat/jackson-dataformat-cbor(Maven) | >= 2.16.0, <= 2.18.9 | No fix listed |
| com.fasterxml.jackson.dataformat/jackson-dataformat-cbor(Maven) | >= 2.19.0, <= 2.21.5 | No fix listed |
| com.fasterxml.jackson.dataformat/jackson-dataformat-cbor(Maven) | >= 2.22.0, <= 2.22.1 | No fix listed |
| tools.jackson.dataformat/jackson-dataformat-cbor(Maven) | >= 3.0.0, <= 3.1.5 | No fix listed |
| tools.jackson.dataformat/jackson-dataformat-cbor(Maven) | >= 3.2.0, <= 3.2.1 | No fix listed |
| debian/jackson-dataformat-cbor(Debian:12) | All versions | No fix listed |
| debian/jackson-dataformat-cbor(Debian:12) | = 2.7.8-5 | No fix listed |
| debian/jackson-dataformat-cbor(Debian:12) | = 2.7.8-5.1 | No fix listed |
| debian/jackson-dataformat-cbor(Debian:13) | All versions | No fix listed |
| debian/jackson-dataformat-cbor(Debian:13) | = 2.7.8-5.1 | No fix listed |
| debian/jackson-dataformat-cbor(Debian:14) | All versions | No fix listed |
| debian/jackson-dataformat-cbor(Debian:14) | = 2.7.8-5.1 | No fix listed |
| ubuntu/jackson-dataformat-cbor(Ubuntu:22.04) | All versions | No fix listed |
| ubuntu/jackson-dataformat-cbor(Ubuntu:24.04) | All versions | No fix listed |
| ubuntu/jackson-dataformat-cbor(Ubuntu:26.04) | All versions | No fix listed |
| ubuntu/jackson-dataformat-cbor(Ubuntu:26.10) | All versions | No fix listed |
References
- GHSA-3v8f-v6vx-fmrm exploit vendor-advisory
- FasterXML/jackson-dataformats-binary#725 patch
- CVE-2026-68496 (Smile parser, same advisory) related
- jackson-dataformats-binary 2.18.10 release notes (maps #725/#726 to CVE IDs) release-notes
- Red Hat CVE page vendor-advisory
- Red Hat Bugzilla 2544838 issue-tracking
- www.cve.org
- nvd.nist.gov
- Debian Security Tracker CVE-2026-68495 vendor-advisory
- Ubuntu CVE tracker vendor-advisory
- ENISA EUVD EUVD-2026-90977 third-party-advisory