PoC Monitor
← All CVEs
CVE-2026-89425published 23 Sep 2026 02:06 UTCData: JSON · API

FasterXML jackson-core

jackson-core: UTF8DataInputJsonParser._reportInvalidToken() does not honor maxErrorTokenLength, allowing unbounded StringBuilder growth

UTF8DataInputJsonParser._reportInvalidToken() in FasterXML jackson-core builds the offending-token text for its error message by appending Java identifier characters to a StringBuilder in a loop that has no upper bound. Unlike the three sibling parser implementations, including UTF8StreamJsonParser, it never consults ErrorReportConfiguration.getMaxErrorTokenLength() (default 256). A malformed token supplied to a parser created through JsonFactory.createParser(DataInput) is therefore accumulated in full. No StreamReadConstraints setting mitigates this: maxDocumentLength cannot be applied to DataInput sources at all, and maxStringLength does not cover this path because the accumulation bypasses ReadConstrainedTextBuffer. The reporter measured a 20,000,109-character exception message from a 20-million-character malformed token on the DataInput path, against 367 characters for identical input on the InputStream path. Scaling the payload drives the StringBuilder, which also incurs byte-to-char expansion and internal array doubling, to many times the raw payload size and can trigger OutOfMemoryError for the whole JVM. UTF8DataInputJsonParser was introduced in 2.8.0 together with createParser(DataInput); releases before 2.8.0 do not contain the affected class.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.5high · scored by CNA · CWE-770
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record, GitHub Security Advisories and the vendor's references.

Affected

FasterXML jackson-core
  • >= 2.8.0, <= 2.18.10
  • >= 2.19.0, <= 2.21.6
  • >= 2.22.0, <= 2.22.2
FasterXML jackson-core
  • >= 3.0.0, <= 3.1.6
  • >= 3.2.0, <= 3.2.2
com.fasterxml.jackson.core:jackson-core (Maven)
  • >= 2.19.0, < 2.21.7

Fixed in 2.21.7

from GitHub Security Advisory GHSA-7hhh-6rmp-j9qf

com.fasterxml.jackson.core:jackson-core (Maven)
  • >= 2.22.0, < 2.22.3

Fixed in 2.22.3

from GitHub Security Advisory GHSA-7hhh-6rmp-j9qf

tools.jackson.core:jackson-core (Maven)
  • >= 3.0.0, < 3.1.7

Fixed in 3.1.7

from GitHub Security Advisory GHSA-7hhh-6rmp-j9qf

tools.jackson.core:jackson-core (Maven)
  • >= 3.2.0, < 3.2.3

Fixed in 3.2.3

from GitHub Security Advisory GHSA-7hhh-6rmp-j9qf

com.fasterxml.jackson.core:jackson-core (Maven)
  • >= 2.8.0, < 2.18.11

Fixed in 2.18.11

from GitHub Security Advisory GHSA-7hhh-6rmp-j9qf

Mitigation

Upgrade to com.fasterxml.jackson.core:jackson-core 2.18.11, 2.21.7 or 2.22.3, or to tools.jackson.core:jackson-core 3.1.7 or 3.2.3. The 2.8.x through 2.17.x, 2.19.x, 2.20.x and 3.0.x lines received no fix on their own branch and are no longer maintained upstream; consumers of those lines must move forward to a maintained release.

Workaround

No StreamReadConstraints or ErrorReportConfiguration setting mitigates this issue on the affected code path. Where possible, avoid JsonFactory.createParser(DataInput) for attacker-supplied content and use createParser(InputStream), createParser(Reader) or a byte-array overload instead; those parser implementations enforce maxErrorTokenLength correctly. Otherwise, bound input size ahead of the parser and cap JVM heap so that a single request cannot exhaust process memory.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published23 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.