CVE-2026-68495 Affecting jackson-dataformat-xml package, versions <2.18.11-150200.5.8.1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-SLES154-JACKSONDATAFORMATXML-20305492
- published30 Sept 2026
- disclosed29 Sept 2026
Introduced: 29 Sep 2026
NewCVE-2026-68495 (opens in a new tab)How to fix?
Upgrade SLES:15.4 jackson-dataformat-xml to version 2.18.11-150200.5.8.1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream jackson-dataformat-xml package and not the jackson-dataformat-xml package as distributed by SLES.
See How to fix? for SLES:15.4 relevant fixed versions and status.
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.
References
- https://www.suse.com/security/cve/CVE-2026-68495.html
- https://bugzilla.suse.com/1280125
- https://bugzilla.suse.com/1282639
- https://github.com/FasterXML/jackson-dataformats-binary/blob/2.18/release-notes/VERSION-2.x
- https://github.com/FasterXML/jackson-dataformats-binary/issues/725
- https://www.cve.org/CVERecord?id=CVE-2026-68496
- https://github.com/FasterXML/jackson-dataformats-binary/security/advisories/GHSA-3v8f-v6vx-fmrm