VDB

CVE-2026-68495

CVE-2026-68495 PUBLISHED CVSS 7.5 HIGH

Reported by herodevs · Published October 1, 2026

jackson-dataformat-cbor is fixed in 2.22.1, 2.21.5 and 2.18.9 (Maven Central)

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
com.fasterxml.jackson.dataformat:jackson-dataformat-cborMaven Central2.22.1, 2.21.5, 2.18.9
tools.jackson.dataformat:jackson-dataformat-cborMaven Central3.2.1, 3.1.5

Risk scores

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

Affected products

VendorProductVersions
FasterXMLjackson-dataformats-binary2.16.0, 2.19.0, 2.22.0
FasterXMLjackson-dataformats-binary3.0.0, 3.2.0
FasterXMLjackson-dataformats-binary2.16.0, 2.19.0, 2.22.0
FasterXMLjackson-dataformats-binary3.0.0, 3.2.0

Timeline

  • Sep 24, 2026 CVE Published
  • Oct 2, 2026 EPSS Score (18 in total, the first dated here)
  • Oct 2, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-68495
vulnetix vdb fixes CVE-2026-68495

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-68495/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›