CVE-2026-68498

jackson-core: Delayed maxNameLength enforcement for char-backed input (ReaderBasedJsonParser) allows memory-exhaustion denial of service

  • High 7.5

Description

StreamReadConstraints.maxNameLength (default 50,000 characters) is intended to bound how much memory a single JSON Object property name can consume while being parsed, independently of the much larger maxStringLength (default 100,000,000 characters) that bounds ordinary string values. For parsers built over character input — Reader, String or char[] sources, all served by ReaderBasedJsonParser — that bound is not applied while the name is being accumulated. The code path instead re-uses the string-value length check, which is roughly 2000x larger by default. In the character-input slow path, ReaderBasedJsonParser._parseName2() accumulates the name into the TextBuffer and, when a segment fills, calls TextBuffer.finishCurrentSegment(), which validates only maxStringLength. The correct check, StreamReadConstraints.validateNameLength(int), is reached afterwards in CharsToNameCanonicalizer.findSymbol(), once the entire name has been scanned to its closing quote. By that point the full name — up to maxStringLength characters — has already been buffered in memory. A remote attacker who can have a single sufficiently long JSON Object property name parsed through this path can force allocation on the order of 100,000,000 characters (approximately 200 MB, with segment bookkeeping pushing real peak usage higher) before any StreamConstraintsException is thrown, instead of the approximately 50,000-character (about 100 KB) bound the API promises. Repeating this across concurrent requests can exhaust the heap and crash the process. No authentication or user interaction is required. Because StreamReadConstraints.maxDocumentLength is disabled by default (-1), nothing else bounds the token first, so the issue is exploitable under default configuration. Byte-input parsers are not affected: UTF8StreamJsonParser, UTF8DataInputJsonParser and the non-blocking (async) parsers re-validate maxNameLength on every growth of the name-decode buffer via ParserBase._growNameDecodeBuffer(), rejecting an oversized name after allocating only tens of kilobytes. Applications are exposed when untrusted JSON is parsed from a String, Reader or char[] — for example an HTTP request body already read into a String — rather than from raw UTF-8 bytes. This issue affects com.fasterxml.jackson.core:jackson-core from 2.16.0 and tools.jackson.core:jackson-core from 3.0.0. Releases before 2.16.0 are not affected, because StreamReadConstraints.maxNameLength was first introduced in jackson-core 2.16.0.

Key facts

Published
16 Oct 2026
Last changed
20 Oct 2026
Assigned by
HeroDevs
EPSS
0.652% likely to be exploited in the next 30 days, higher than 51.971% of CVEs (scores for 18 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.5CVSS 3.1, Highfrom the CNA (HeroDevs)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
FasterXMLjackson-core
  • Default status: unaffected
  • 2.16.0 up to but excluding 2.18.10 (affected)
  • 2.18.10 (unaffected)
  • 2.19.0 up to but excluding 2.21.6 (affected)
  • 2.21.6 (unaffected)
  • 2.22.0 up to but excluding 2.22.2 (affected)
  • 2.22.2 (unaffected)
FasterXMLjackson-core
  • Default status: unaffected
  • 3.0.0 up to but excluding 3.1.6 (affected)
  • 3.1.6 (unaffected)
  • 3.2.0 up to but excluding 3.2.2 (affected)
  • 3.2.2 (unaffected)

Timeline

  1. 29 Jul 2026 Fix merged upstream via FasterXML/jackson-core#1643
  2. 14 Aug 2026 Fix released in jackson-core 2.21.6, 3.1.6 and 3.2.2
  3. 15 Aug 2026 Fix released in jackson-core 2.18.10
  4. 16 Aug 2026 Fix released in jackson-core 2.22.2
  5. 11 Sep 2026 GHSA-649p-m576-vr99 published by the maintainer in FasterXML/jackson-core
  6. 16 Oct 2026 Published

Weakness

References