Skip to content
VulniPulse
Critical 2 vendors · 2 advisories

CVE-2026-83557: jackson-databind omits java.lang.Comparable from DefaultBaseTypeLimitingValidator's unsafe base types

CVE-2026-83557 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Critical
CVSS base score
5.6 (Red Hat)
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L · base score 5.6, scored by HeroDevsAttack vector: network. Attack complexity: high. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: low. Integrity impact: low. Availability impact: low.
Weakness
  • CWE-502 Deserialization of Untrusted Data
  • CWE-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes
EPSS
0.72% chance of exploitation in the next 30 days (54th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: proof of concept exists. Automatable: no. Technical impact: partial. CISA, .
Fixed releases
  • Red Hat: 2.18.10, 2.21.6, 2.22.2, 3.1.6, 3.2.2, com.fasterxml.jackson.core/jackson-databind:2.21.7.redhat-00001 and 2 more in the advisory
Vendor advisories
2 from NetApp, Red Hat
Assigned by
HeroDevs (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-83557; each belongs to its advisory, not to every product listed. How records are collected and checked.

Description

DefaultBaseTypeLimitingValidator is the PolymorphicTypeValidator applied automatically whenever @JsonTypeInfo is used without an explicitly configured custom validator. It denies polymorphic resolution only for a fixed set of "unsafe base types", and its isSafeSubType method returns true unconditionally for every base type outside that set. java.lang.Comparable was absent from the list despite being implemented by a very large fraction of JDK and application classes, comparable in breadth to java.io.Serializable, which is on the list for that reason. An application declaring an @JsonTypeInfo-annotated property or class with Comparable as its base type, and no custom PolymorphicTypeValidator, will accept a type identifier for essentially any class implementing Comparable. This yields an attacker-controlled object instantiation primitive; a demonstrated case constructs a java.io.File for an arbitrary attacker-chosen path, which becomes path-traversal-adjacent if the application subsequently calls path-sensitive methods on the value. No class implementing Comparable has been identified that yields code execution through deserialization alone. Global Default Typing via activateDefaultTyping is not affected, because that method structurally requires an explicit PolymorphicTypeValidator argument. This affects com.fasterxml.jackson.core:jackson-databind from 2.11.0 before 2.18.10, from 2.19.0 before 2.21.6, and from 2.22.0 before 2.22.2, and tools.jackson.core:jackson-databind from 3.0.0 before 3.1.6 and from 3.2.0 before 3.2.2. Users should upgrade to 2.18.10, 2.21.6, 2.22.2, 3.1.6, or 3.2.2.

Text from the CVE.org record (HeroDevs).

How do I fix CVE-2026-83557?

Upgrade to a fixed release named by the vendor:

  • Red Hat: 2.18.10, 2.21.6, 2.22.2, 3.1.6, 3.2.2, com.fasterxml.jackson.core/jackson-databind:2.21.7.redhat-00001
  • If immediate upgrade is not possible, audit for @JsonTypeInfo properties typed as java.lang.Comparable without a custom PolymorphicTypeValidator. Narrow the type or add a validator that denies java.io.File and similar Comparable implementations. This doesn't apply to global default typing (activateDefaultTyping), which already requires an explicit validator. (Red Hat)
  • Upgrade to jackson-databind 2.18.10, 2.21.6, 2.22.2 (com.fasterxml.jackson.core) or 3.1.6, 3.2.2 (tools.jackson.core). The fix adds java.lang.Comparable to the UnsafeBaseTypes denylist in DefaultBaseTypeLimitingValidator, so polymorphic resolution against a Comparable base type is denied outright. Applications that legitimately need polymorphic handling of a Comparable-typed property must configure an explicit PolymorphicTypeValidator, for example a BasicPolymorphicTypeValidator with an allow-list of permitted subtypes. (CVE.org record)
  • Workaround: Configure an explicit restrictive PolymorphicTypeValidator rather than relying on the default validator, or avoid declaring java.lang.Comparable as the base type of an @JsonTypeInfo-annotated property or class. Narrowing the declared base type to an application-specific interface also removes the exposure. (CVE.org record)

Vendor advisories for CVE-2026-83557

NetApp

1 advisory
  • Advisory severityCritical9.2

    Critical [CVE-2026-101898 +79] November 2026 IBM Cognos Analytics Vulnerabilities in NetApp Products

    NTAP-20261118-0008Source published Source updated

    This bulletin covers 80 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.

    There are vulnerabilities in multiple Open Source Software (OSS) components consumed by IBM Cognos Analytics versions 12.1.0 through 12.1.3 FP3, 12.0 through 12.0.4 FP3 and 11.2.0 through 11.2.4 IF7 which when successfully exploited could lead to disclosure of sensitive information, addition or modification of data, or Denial of Service (DoS). NetApp states there is no workaround available at this time.

    Affected products in this advisory
    No product details extracted. Check the source bulletin.
    Source-reported affected versions
    • 12.1.0
    • 12.1.3
    • 12.0
    • 12.0.4

    2 more entries in the full advisory.

    Source-reported fixed versions
    No fixed-version detail extracted. This does not mean no fix exists.
    Mitigation guidance
    No mitigation guidance extracted; consult the source.

Red Hat

1 advisory
  • Advisory severityMedium5.6

    Medium [CVE-2026-83557] com.fasterxml.jackson.core/jackson-databind: tools.jackson.core/jackson-databind: jackson-databind: Path traversal via incomplete type validation

    CVE-2026-83557Source published Source updated

    DefaultBaseTypeLimitingValidator is the PolymorphicTypeValidator applied automatically whenever @JsonTypeInfo is used without an explicitly configured custom validator. It denies polymorphic resolution only for a fixed set of "unsafe base types", and its isSafeSubType method returns true unconditionally for every base type outside that set. java.lang. Comparable was absent from the list despite being implemented by a very large fraction of JDK and application classes, comparable in breadth to java.io.Serializable, which is on the list for that reason. An application declaring an @JsonTypeInfo-annotated property or class with Comparable as its base type, and no custom PolymorphicTypeValidator, will accept a type identifier for essentially any class implementing Comparable. This yields an…

    Affected products in this advisory
    • Red Hat build of Quarkus 3.27.6.redhat
    • Red Hat build of Quarkus 3.33.4.redhat
    • Exploit Intelligence
    • OpenShift Developer Tools and Services

    36 more entries in the full advisory.

    Source-reported affected versions
    • < 2.11.0
    • < 2.18.10
    • < 2.19.0
    • < 2.21.6

    6 more entries in the full advisory.

    Source-reported fixed versions
    • 2.18.10
    • 2.21.6
    • 2.22.2
    • 3.1.6

    4 more entries in the full advisory.

    Mitigation guidance
    • If immediate upgrade is not possible, audit for @JsonTypeInfo properties typed as java.lang.Comparable without a custom PolymorphicTypeValidator. Narrow the type or add a validator that denies java.io.File and similar Comparable implementations. This doesn't apply to global default typing (activateDefaultTyping), which already requires an explicit validator.

References

Timeline

  1. CVE record published
  2. CVE record last updated
  3. First vendor advisory listed by VulniPulse

All NetApp advisories

Get an email when NetApp publishes the next one.

See NetApp's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about NetApp