CVE-2026-83557

MEDIUMPre-NVD 5.65.6
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
5.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.6Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.6
EG Score
5.6(medium)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity56% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 8, 2026

Advisory Details (4)

Auto-updated Sep 1, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit.
github_commit

commit eb3b7fc0f9c0 (FasterXML/jackson-databind)

Fix landed in FasterXML/jackson-databind commit eb3b7fc0f9c0 — awaiting tagged release

https://github.com/FasterXML/jackson-databind/commit/eb3b7fc0f9c0d27f471550ac3316b17d1987388f
generic

Add `java.lang.Comparable` in set of "unsafe" polymorphic base types [CVE-2026-83557] · Issue #6156 · FasterXML/jackson-databind · GitHub

https://github.com/FasterXML/jackson-databind/issues/6156
github_pr

Add `java.lang.Comparable` as an "unsafe" polymorphic base type

Fix merged in FasterXML/jackson-databind PR #6155 on 2026-08-11 — awaiting tagged release

https://github.com/FasterXML/jackson-databind/pull/6155
github Patch Available🟡 PoC Available

Comparable missing from DefaultBaseTypeLimitingValidator's unsafe base types (incomplete PolymorphicTypeValidator denylist) · Advisory · FasterXML/jackson-databind · GitHub

https://github.com/FasterXML/jackson-databind/security/advisories/GHSA-gx83-3vf8-gh7j

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
jackson-databind2.14.0+ds-1, 2.14.0+ds-2, 2.14.0-1, 2.14.0-1+deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
jackson-databind2.14.0+ds-1, 2.14.0+ds-1+deb13u1, 2.14.0+ds-2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
jackson-databind2.14.0+ds-1, 2.14.0+ds-2

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 02:05 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 01:49 UTCEG score recompute
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-17 01:33 UTCEG score recompute
  6. 2026-09-16 14:09 UTCEPSS rescore
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-16 01:17 UTCEG score recompute
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-14 00:44 UTCEG score recompute
  12. 2026-09-13 00:28 UTCEG score recompute
  13. 2026-09-12 00:11 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-10 23:54 UTCEG score recompute
  17. 2026-09-09 23:37 UTCEG score recompute
  18. 2026-09-08 22:01 UTCEPSS rescore
  19. 2026-09-07 21:25 UTCEG score recompute
  20. 2026-09-06 21:10 UTCEG score recompute
  21. 2026-09-06 13:48 UTCEPSS rescore
  22. 2026-09-05 20:51 UTCEG score recompute
  23. 2026-09-05 15:31 UTCEPSS rescore
  24. 2026-09-04 20:35 UTCEG score recompute
  25. 2026-09-04 05:07 UTCEPSS rescore
Show 7 more
  1. 2026-09-02 20:00 UTCEG score recompute
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 18:24 UTCEG score recompute
  4. 2026-09-01 17:49 UTCEG score recompute
  5. 2026-09-01 15:38 UTCEG score recompute
  6. 2026-09-01 15:04 UTCEG score recompute
  7. 2026-09-01 15:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-83557?
CVE-2026-83557 is a medium vulnerability published on September 1, 2026. 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…
When was CVE-2026-83557 disclosed?
CVE-2026-83557 was first published in the National Vulnerability Database on September 1, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-83557 actively exploited?
CVE-2026-83557 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.3% of all scored CVEs.
What is the CVSS score of CVE-2026-83557?
CVE-2026-83557 has a CVSS v3 base score of 5.6 (NVD).
How do I remediate CVE-2026-83557?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-83557, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-83557

Explore →

Is Your Infrastructure Affected by CVE-2026-83557?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.