Skip to main content
VulnerabilityPublished

CVE-2026-54512: FasterXML jackson-databind · Incomplete List of Disallowed Inputs

Affects FasterXML jackson-databindSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High · fixed in 3.1.4 : patch FasterXML jackson-databind soon.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 64% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.1.4, 2.21.4, 2.18.8
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade jackson-databind and com.fasterxml.jackson.core/jackson-databind to 3.1.4, 2.21.4 or 2.18.8.

Affected software

ProductAffectedFixed in
FasterXMLjackson-databindAffected
  • >=3.0.0 <3.1.4
Fixed in
  • 3.1.4
FasterXMLjackson-databindAffected
  • >=2.19.0 <2.21.4
Fixed in
  • 2.21.4
FasterXMLjackson-databindAffected
  • >=2.10.0 <2.18.8
Fixed in
  • 2.18.8
Mavencom.fasterxml.jackson.core/jackson-databindpkg:maven/com.fasterxml.jackson.core/jackson-databindOther threatsAffected
  • >=2.10.0 <2.18.8
  • >=2.18.0 <2.21.4
  • >=3.0.0 <3.1.4
Fixed in
  • 2.18.8
  • 2.21.4
  • 3.1.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in jackson-databind versions 2.18.8, 2.21.4, and 3.1.4. Users should upgrade to one of these versions or later to remediate the issue. No official temporary fixes or workarounds are provided. Patch status is confirmed by the vendor advisory. Users should verify upgrade paths and test accordingly.

Description

jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.10.0 until 2.18.8, 2.21.4, and 3.1.4, jackson-databind's PolymorphicTypeValidator (PTV) is the primary safety mechanism guarding polymorphic deserialization. When polymorphic typing is enabled and a type identifier contains generic parameters (i.e. the type ID string contains <), DatabindContext._resolveAndValidateGeneric() validates only the raw container class name (the substring before <) against the configured PTV. If the container type is approved, the method parses the full canonical type string via TypeFactory.constructFromCanonical() and returns the fully parameterized type without ever validating the nested type arguments against the PTV. The nested type arguments are then resolved, instantiated, and populated as beans during deserialization. An attacker who controls the type ID can therefore place a denied class as a generic type parameter of an allowed container — for example java.util.ArrayList<com.evil.Gadget> when only java.util.ArrayList is allow-listed. The container passes the PTV check; com.evil.Gadget is loaded via Class.forName(name, true, loader), instantiated, and its properties are set from attacker-controlled JSON. This completely bypasses an explicitly configured PTV allow-list. This vulnerability is fixed in 2.18.8, 2.21.4, and 3.1.4.

References

Community reviews

Loading reviews…