CVE-2026-54513

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 52% 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: cna:github_m, epss
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.1Exploit: NoneExposed: 0

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

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)
EPSS
47.8%
KEV
Not listed

Published

June 23, 2026

Last Modified

July 6, 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(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 44× 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-07 01:10 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 12:33 UTCEG score recompute
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 23:56 UTCEG score recompute
  8. 2026-07-05 11:19 UTCEG score recompute
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 22:43 UTCEG score recompute
  12. 2026-07-04 10:05 UTCEG score recompute
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-03 21:28 UTCEG score recompute
  16. 2026-07-03 08:50 UTCEG score recompute
  17. 2026-07-02 20:13 UTCEG score recompute
  18. 2026-07-02 07:35 UTCEG score recompute
  19. 2026-07-01 18:58 UTCEG score recompute
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-07-01 06:21 UTCEG score recompute
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 17:44 UTCEG score recompute
  24. 2026-06-30 05:07 UTCEG score recompute
  25. 2026-06-29 16:28 UTCEG score recompute
Show 19 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-29 03:51 UTCEG score recompute
  4. 2026-06-28 15:05 UTCEG score recompute
  5. 2026-06-28 14:07 UTCEPSS rescore
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-28 04:56 UTCEPSS rescore
  8. 2026-06-28 02:28 UTCEG score recompute
  9. 2026-06-27 13:51 UTCEG score recompute
  10. 2026-06-27 03:08 UTCEPSS rescore
  11. 2026-06-27 01:14 UTCEG score recompute
  12. 2026-06-26 12:38 UTCEG score recompute
  13. 2026-06-26 00:01 UTCEG score recompute
  14. 2026-06-25 13:49 UTCEPSS rescore
  15. 2026-06-25 11:24 UTCEG score recompute
  16. 2026-06-24 22:46 UTCEG score recompute
  17. 2026-06-24 14:05 UTCEPSS rescore
  18. 2026-06-24 10:10 UTCEG score recompute
  19. 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 6, 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 47.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54513?
CVE-2026-54513 has a CVSS v4.0 base score of 8.1 (CNA self-assessment; NVD's own analysis pending).
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

Explore the affected products and dependency analysis for 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