CVE-2026-54513

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 50% 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
Trending — Patch released this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

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, BasicPolymorphicTypeValidator.Builder.allowIfSubTypeIsArray() allowlists any array type based only on clazz.isArray(), without validating the array's component (element) type against the configured allowlist. A PTV built with allowIfSubTypeIsArray() plus an explicit concrete-type allowlist therefore still permits EvilType[] even though EvilType is not allowlisted. When Jackson deserializes the elements and no per-element type IDs are present, it instantiates the component type directly with no further PTV check, bypassing the allowlist. This vulnerability is fixed in 2.18.8, 2.21.4, and 3.1.4.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

June 23, 2026

Last Modified

July 23, 2026

Advisory Details (6)

Auto-updated Jun 24, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

Array subtype allowlist bypass in BasicPolymorphicTypeValidator (allowIfSubTypeIsArray) in jackson-databind · Advisory · FasterXML/jackson-databind · GitHub

https://github.com/FasterXML/jackson-databind/security/advisories/GHSA-rmj7-2vxq-3g9f
github_pr

Backport fix for #5981 in 2.18 branch

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

https://github.com/FasterXML/jackson-databind/pull/5984
generic

Fix #5981: `BasicPolymorphicTypeValidator` setting `allowIfSubTypeIsArray()` should validate element type by cowtowncoder · Pull Request #5983 · FasterXML/jackson-databind · GitHub

https://github.com/FasterXML/jackson-databind/issues/5983
generic

`BasicPolymorphicTypeValidator` setting `allowIfSubTypeIsArray()` should validate element type [CVE-2026-54513] · Issue #5981 · FasterXML/jackson-databind · GitHub

https://github.com/FasterXML/jackson-databind/issues/5981
github_commit

commit 24529da29fdf (FasterXML/jackson-databind)

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

https://github.com/FasterXML/jackson-databind/commit/24529da29fdf46ff94ca38de9ebf31cd188f5e8e
github_commit

commit 01d1692c8d0e (FasterXML/jackson-databind)

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

https://github.com/FasterXML/jackson-databind/commit/01d1692c8d0ed03e51a0e3c4f8a9e6908e4931e5

Vendor Advisories for CVE-2026-54513(13)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatjackson-databind-0:2.21.4-1.el9_42026-07-23redhat
redhatpki-deps:10.6-8060020260720025549.ad008a3a2026-07-23redhat
redhatjackson-databind-0:2.21.4-1.el9_22026-07-23redhat
redhatjackson-databind-0:2.21.4-1.el9_62026-07-23redhat
redhatpki-deps:10.6-8040020260720064222.522a0ee42026-07-23redhat
redhatpki-deps:10.6-8080020260714161755.63b345852026-07-23redhat
redhatdogtag-pki-0:11.6.0-2.el10_02026-07-23redhat
redhatdogtag-pki-0:11.9.0-4.el10_22026-07-22redhat
redhatpki-deps:10.6-8100020260714102233.489197e62026-07-22redhat
redhatjackson-databind2026-07-20redhat
redhatjackson-databind-0:2.21.4-1.el9_82026-07-16redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
com.fasterxml.jackson.core:jackson-databind—3.1.4—
tools.jackson.core:jackson-databind3.0.0 ... 3.1.3 (10 versions)3.1.4—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 65× 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-07-27 07:22 UTCVendor advisory
  2. 2026-07-26 18:44 UTCEG score recompute
  3. 2026-07-26 18:44 UTCVendor advisory
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 05:12 UTCEG score recompute
  6. 2026-07-26 05:12 UTCVendor advisory
  7. 2026-07-25 14:18 UTCEPSS rescore
  8. 2026-07-24 14:18 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 03:19 UTCEG score recompute
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-21 15:25 UTCEPSS rescore
  13. 2026-07-20 17:08 UTCEPSS rescore
  14. 2026-07-19 14:31 UTCEPSS rescore
  15. 2026-07-19 14:31 UTCEPSS rescore
  16. 2026-07-19 02:29 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-17 02:46 UTCVendor advisory
  19. 2026-07-16 17:03 UTCEPSS rescore
  20. 2026-07-16 13:32 UTCVendor advisory
  21. 2026-07-16 00:43 UTCVendor advisory
  22. 2026-07-15 16:57 UTCEPSS rescore
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 12:07 UTCVendor advisory
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 44 more
  1. 2026-07-15 02:00 UTCEPSS rescore
  2. 2026-07-14 22:48 UTCVendor advisory
  3. 2026-07-14 10:09 UTCVendor advisory
  4. 2026-07-13 22:31 UTCEPSS rescore
  5. 2026-07-13 21:32 UTCVendor advisory
  6. 2026-07-13 08:55 UTCVendor advisory
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-12 20:19 UTCVendor advisory
  10. 2026-07-12 07:41 UTCVendor advisory
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-11 19:04 UTCVendor advisory
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-11 06:27 UTCVendor advisory
  16. 2026-07-10 17:46 UTCVendor advisory
  17. 2026-07-10 05:08 UTCVendor advisory
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 16:17 UTCVendor advisory
  21. 2026-07-09 03:40 UTCVendor advisory
  22. 2026-07-08 15:16 UTCEPSS rescore
  23. 2026-07-08 15:16 UTCEPSS rescore
  24. 2026-07-07 13:46 UTCEPSS rescore
  25. 2026-07-07 13:46 UTCEPSS rescore
  26. 2026-07-06 16:27 UTCEPSS rescore
  27. 2026-07-06 16:27 UTCEPSS rescore
  28. 2026-07-06 02:23 UTCEPSS rescore
  29. 2026-07-06 02:23 UTCEPSS rescore
  30. 2026-07-05 02:31 UTCEPSS rescore
  31. 2026-07-05 02:30 UTCEPSS rescore
  32. 2026-07-04 06:31 UTCEPSS rescore
  33. 2026-07-04 06:31 UTCEPSS rescore
  34. 2026-07-01 15:07 UTCEPSS rescore
  35. 2026-06-30 23:22 UTCEPSS rescore
  36. 2026-06-29 14:06 UTCEPSS rescore
  37. 2026-06-29 14:06 UTCEPSS rescore
  38. 2026-06-28 14:07 UTCEPSS rescore
  39. 2026-06-28 04:56 UTCEPSS rescore
  40. 2026-06-28 04:56 UTCEPSS rescore
  41. 2026-06-27 03:08 UTCEPSS rescore
  42. 2026-06-25 13:49 UTCEPSS rescore
  43. 2026-06-24 14:05 UTCEPSS rescore
  44. 2026-06-23 21:31 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54513?
CVE-2026-54513 is a high vulnerability published on June 23, 2026. 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, BasicPolymorphicTypeValidator.Builder.allowIfSubTypeIsArray() allowlists any array type based only on clazz.isArray(), without validating…
When was CVE-2026-54513 disclosed?
CVE-2026-54513 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54513 actively exploited?
CVE-2026-54513 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 50.2% of all scored CVEs.
What is the CVSS score of CVE-2026-54513?
CVE-2026-54513 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-54513?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54513, 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-54513

Explore →

Is Your Infrastructure Affected by CVE-2026-54513?

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

Start Free Scan →Browse All CVEs