Skip to content
NewA calmer, faster ZeroHour

CVE-2026-110879

Polymorphic type-ID validation bypass in jackson-databind

CVSS 3.1
9.8 critical
EPSS
—
Published
·
Modified
Analyze CVE-2026-110879 with Vani AIImpact, affected versions, exploitation status, mitigations and detection

jackson-databind checks the outer class of a class-name type ID but can accept attacker-chosen classes in generic arguments, including classes rejected as direct type IDs. This is an incomplete fix of CVE-2026-54512. A remote attacker who supplies JSON to annotation-based class-name polymorphism or configured default typing can deserialize those classes and their properties. With Spring and attacker-controlled XML, a Map property path can reach ProcessBuilder.start() and run commands as the application.

What to do: No fixed jackson-databind version is stated for CVE-2026-110879. Apply the vendor update for this CVE if one is issued.

ProductAffected
com.fasterxml.jackson.core jackson-databind2.10.0 and later; before 2.10.0 not affected
tools.jackson.core jackson-databind3.0.0 and later
Estimated exposure
No basis for an estimate.

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description · NVD

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 accepts HashMap ; 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.

Weakness
CWE-502
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

In the news

1 story