UBUNTU-CVE-2026-89425 (CVE-2026-89425)
Vulnerability from osv_ubuntu – Published: 2026-09-23 03:17 – Updated: 2026-09-23 03:17 – Source websiteUTF8DataInputJsonParser._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.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libjackson2-core-java",
"binary_version": "2.4.2-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "jackson-core",
"purl": "pkg:deb/ubuntu/jackson-core@2.4.2-2?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.4.2-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libjackson2-core-java",
"binary_version": "2.9.8-3~18.04"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "jackson-core",
"purl": "pkg:deb/ubuntu/jackson-core@2.9.8-3~18.04?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.8.6-1",
"2.9.1-1",
"2.9.4-1",
"2.9.8-3~18.04"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libjackson2-core-java",
"binary_version": "2.10.1-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "jackson-core",
"purl": "pkg:deb/ubuntu/jackson-core@2.10.1-1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.9.8-3",
"2.10.0-1",
"2.10.1-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libjackson2-core-java",
"binary_version": "2.13.0-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "jackson-core",
"purl": "pkg:deb/ubuntu/jackson-core@2.13.0-2?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.12.1-1",
"2.13.0-1",
"2.13.0-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libjackson2-core-java",
"binary_version": "2.14.1-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "jackson-core",
"purl": "pkg:deb/ubuntu/jackson-core@2.14.1-1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.14.1-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libjackson2-core-java",
"binary_version": "2.14.1-1build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "jackson-core",
"purl": "pkg:deb/ubuntu/jackson-core@2.14.1-1build1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.14.1-1",
"2.14.1-1build1"
]
}
],
"aliases": [],
"details": "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.",
"id": "UBUNTU-CVE-2026-89425",
"modified": "2026-09-23T03:17:00Z",
"published": "2026-09-23T03:17:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-89425"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-89425"
},
{
"type": "REPORT",
"url": "https://github.com/FasterXML/jackson-core/security/advisories/GHSA-7hhh-6rmp-j9qf"
},
{
"type": "REPORT",
"url": "https://github.com/FasterXML/jackson-core/pull/1698"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-89425"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.