jackson-databind: Deserialization of Untrusted Data (CVE-2026-110879)
Published Sources: BSI
What is affected, what to do
jackson-databind validates the outer class of a class-name type ID but accepts attacker-selected classes inside its generic arguments, even when those classes violate the declared type or would be rejected as direct type IDs. This bypasses the generic-argument validation added for CVE-2026-54512 (GHSA-j3rv-43j4-c7qm), of which this is an incomplete fix.
Update FasterXML Jackson-databind to version 2.18.12, FasterXML Jackson-databind to version 2.21.8, FasterXML Jackson-databind to version 2.22.4.
- Affected
- FasterXML Jackson-databind
lt 2.10.0..2.18.12 - FasterXML Jackson-databind
lt 2.19.0..2.21.8 - FasterXML Jackson-databind
lt 2.22.0..2.22.4 - FasterXML Jackson-databind
lt 3.0.0..3.1.8 - FasterXML Jackson-databind
lt 3.2.0..3.2.4
- FasterXML Jackson-databind
- Fixed in
- FasterXML Jackson-databind
2.18.12 - FasterXML Jackson-databind
2.21.8 - FasterXML Jackson-databind
2.22.4 - FasterXML Jackson-databind
3.1.8 - FasterXML Jackson-databind
3.2.4
- FasterXML Jackson-databind
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
9.8
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
9.8
CVSS v3
Severity Critical on the scale from 0 to 10.
Source: BSI
1.2 %
EPSS score
Moderate — model estimates 1-10% exploitation likelihood.
Source: FIRST EPSS, percentile 68.1
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 76.89 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 9.8 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 9.8
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 1.2 %
- Moderate — model estimates 1-10% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 68.1
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-502
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
jackson-databind validates the outer class of a class-name type ID but accepts attacker-selected classes inside its generic arguments, even when those classes violate the declared type or would be rejected as direct type IDs. This bypasses the generic-argument validation added for CVE-2026-54512 (GHSA-j3rv-43j4-c7qm), of which this is an incomplete fix. DatabindContext._resolveAndValidateGeneric() checks the outer class against the declared base type and then passes each argument from the type ID to _validateTypeParameter(), which validates the argument against the outer base type rather than enforcing its corresponding declared generic binding. It also invokes validators with arguments that have not passed the subtype check those validators expect. Under the default DefaultBaseTypeLimitingValidator this accepts an unrelated class inside a generic subtype even when the same class is rejected as a direct type ID. Where an allowIfBaseType(...) rule approves the outer type, Jackson substitutes LaissezFaireSubTypeValidator, so the configured validator no longer restricts the embedded arguments. The element type of a plain array type ID such as [Lpkg.Gadget; is likewise left unvalidated once the array's base type is approved. Affected paths include annotation-based class-name polymorphism with a default Jackson 3.x JsonMapper, configured default typing in both Jackson 2.x and 3.x, and integrations that expose that default typing. The default-validator case requires no application-authored validator: with @JsonTypeInfo(use = Id.CLASS), a direct gadget type ID is rejected as "Not a subtype", while a type ID naming a generic wrapper around the same gadget is accepted and deserialized, including attacker-supplied bean properties. Where class-name default typing permits Map, a property declared as Map<String,String> accepts HashMap<FileSystemXmlApplicationContext,String>; map-key discovery then passes the attacker-controlled JSON property name to the selected class's one-string constructor. With Spring on the classpath and attacker-controlled XML the application can load, that constructor loads the XML and invokes ProcessBuilder.start() under the application account, giving arbitrary command execution. This issue affects com.fasterxml.jackson.core:jackson-databind from 2.10.0 and tools.jackson.core:jackson-databind from 3.0.0. Releases before 2.10.0 are not affected, because PolymorphicTypeValidator was introduced in jackson-databind 2.10.0.
Source: BSI WID Portal
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| FasterXML | jackson-databind |
|
|
| Red Hat | Red Hat Enterprise Linux 10 |
|
|
| Red Hat | Red Hat Enterprise Linux 9 |
|
|
| x.org | libXi |
|
|
| X.org | libXrender |
|
|
| x.org | libXtst |
|
|
| Apache | Camel |
|
|
| Red Hat | Enterprise Linux |
|
|
| Red Hat | Enterprise Linux Quarkus |
|
|
From bundled advisories, not CVE-specific (5)
Product list of a bundled advisory that does not state which product this CVE affects.
| Affected versions | Fixed in | ||
|---|---|---|---|
| — | jackson-databind (FasterXML Jackson, Java) |
|
|
Vendors and products
Affected operating systems
| Linux | ubuntu | libxtst | bionic |
| Linux | ubuntu | libxtst | focal |
| Linux | ubuntu | libxtst | jammy |
| Linux | ubuntu | libxtst | noble |
| Linux | ubuntu | libxtst | resolute |
| Linux | ubuntu | libxtst | stonking |
| Linux | ubuntu | libxtst | xenial |
Weakness classes (CWE)
CWE-502Deserialization of Untrusted Data
Base
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Entry at MITRE CWE-502
References & sources
- access.redhat.comsecurity/cve/CVE-2026-68562Vulnerability database, x_refsource_REDHAT
- bugzilla.redhat.comRHBZ#2466035Issue tracking, x_refsource_REDHAT
- access.redhat.comRHSA-2026:91490Vendor advisory, x_refsource_REDHAT
- access.redhat.comRHSA-2026:91491Vendor advisory, x_refsource_REDHAT
- gitlab.freedesktop.orgxorg/lib/libxi/-/merge_requests/23/diffs?commit_id=e2089ab74882…Patch
- gitlab.freedesktop.orgxorg/lib/libxtst/-/merge_requests/10/diffs?commit_id=16023c8607…Patch
- github.comGHSA-j3rv-43j4-c7qm - original advisory for which this is an incomplete fixrelated
- github.comGHSA-m8xf-2cr7-77ph: PolymorphicTypeValidator bypass via generic type arguments and array element types allows arbitrary class instantiation (CVE-2026-110879)pwn-watch, Vendor advisory
- CVE.org (MITRE)CVE-2026-54512 - original issue for which this is an incomplete fixrelated
- pwn.watchpwn.watch: jackson-databind: PolymorphicTypeValidator bypass via generic type arguments allows arbitrary class instantiation (CVE-2026-110879)pwn-watch
- NVD (NIST)NVD: CVE-2026-110879 (CVSS 3.1 9.8 critical, CWE-502, from the CNA)pwn-watch
- gitlab.freedesktop.orgxorg/lib/libxrender/-/merge_requests/19Patch
- access.redhat.comsecurity/cve/CVE-2026-68563Vulnerability database, x_refsource_REDHAT
- bugzilla.redhat.comRHBZ#2465419Issue tracking, x_refsource_REDHAT
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Received36c7be3b…
CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness type: CWE-502
Description added or changed
Show 7 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —jackson-databind validates the outer class of a class-name type ID but accepts attacker-selected classes inside its generic arguments, even when those classes violate the declared type or would be rejected as direct type IDs. This bypasses the generic-argument validation added for CVE-2026-54512 (GHSA-j3rv-43j4-c7qm), of which this is an incomplete fix. DatabindContext._resolveAndValidateGeneric() checks the outer class against the declared base type and then passes each argument from the type ID to _validateTypeParameter(), which validates the argument against the outer base type rather than enforcing its corresponding declared generic binding. It also invokes validators with arguments that have not passed the subtype check those validators expect. Under the default DefaultBaseTypeLimitingValidator this accepts an unrelated class inside a generic subtype even when the same class is rejected as a direct type ID. Where an allowIfBaseType(...) rule approves the outer type, Jackson substitutes LaissezFaireSubTypeValidator, so the configured validator no longer restricts the embedded arguments. The element type of a plain array type ID such as [Lpkg.Gadget; is likewise left unvalidated once the array's base type is approved. Affected paths include annotation-based class-name polymorphism with a default Jackson 3.x JsonMapper, configured default typing in both Jackson 2.x and 3.x, and integrations that expose that default typing. The default-validator case requires no application-authored validator: with @JsonTypeInfo(use = Id.CLASS), a direct gadget type ID is rejected as "Not a subtype", while a type ID naming a generic wrapper around the same gadget is accepted and deserialized, including attacker-supplied bean properties. Where class-name default typing permits Map, a property declared as Map<String,String> accepts HashMap<FileSystemXmlApplicationContext,String>; map-key discovery then passes the attacker-controlled JSON property name to the selected class's one-string constructor. With Spring on the classpath and attacker-controlled XML the application can load, that constructor loads the XML and invokes ProcessBuilder.start() under the application account, giving arbitrary command execution. This issue affects com.fasterxml.jackson.core:jackson-databind from 2.10.0 and tools.jackson.core:jackson-databind from 3.0.0. Releases before 2.10.0 are not affected, because PolymorphicTypeValidator was introduced in jackson-databind 2.10.0.CVSS added —AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HWeakness type (CWE) added —CWE-502Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/110xxx/CVE-2026-110879.json">CVE-2026-110879</a>Reference added —https://github.com/FasterXML/jackson-databind/security/advisories/GHSA-j3rv-43j4-c7qmReference added —https://github.com/FasterXML/jackson-databind/security/advisories/GHSA-m8xf-2cr7-77phReference added —https://www.cve.org/CVERecord?id=CVE-2026-54512Source identifier: 36c7be3b-2937-45df-85ea-ca7133ea542c
Linked CVEs
| High | CVE-2026-94286 | Out-of-bounds read in libXtst's RECORD reply parser | 7.1 | — |
| High | CVE-2026-93543 | Out-of-bounds read in libXi's XI2 class parser | 7.4 | — |
| High | CVE-2026-88807 | libXrender RenderQueryPictFormats Reply Heap-based Buffer Overflow | — | — |
| Medium | CVE-2026-68563 | Red Hat Enterprise Linux 10: Incorrect Permission Assignment for Critical Resource | 5.5 | — |
| Medium | CVE-2026-68562 | Red Hat Enterprise Linux 10: Externally Controlled Reference to a Resource in Another Sphere | 6.2 | — |
| Critical | CVE-2026-110879 | FasterXML Jackson-databind: Deserialization of Untrusted Data | 9.8 | — |
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-110879"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-110879.svg?lang=en" alt="CVE-2026-110879 – NEOSEC Intel" height="20"></a>