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.9%, top 42% 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
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.2%CVSS: 8.1Exploit: None knownExposed services: Not assessed

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.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

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%
EPSS PROB
1.2%
EPSS %ILE
67th
KEV
Not listed

Published

June 23, 2026

Last Modified

September 14, 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(20)

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

Patch Availability(20)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhateap8-xml-security-0:3.0.6-1.redhat_00001.1.el9eap2026-09-22redhat
redhateap8-xml-security-0:3.0.6-1.redhat_00001.1.el10eap2026-09-22redhat
redhateap8-xml-security-0:3.0.6-1.redhat_00001.1.el8eap2026-09-22redhat
redhatjackson-databind2026-09-21redhat
redhatdevspaces/pluginregistry-rhel9:17877597232026-09-01redhat
redhatrhbk/keycloak-rhel9-operator:26.4-222026-08-05redhat
redhatrhbk-rhel9-operator/rhbk-rhel9-operator2026-08-05redhat
redhatrhbk/keycloak-rhel9-operator:26.6-112026-08-05redhat
redhatredhat-pki:10-8100020260728001635.f93547432026-07-29redhat
redhatcryostat/jfr-datasource-rhel9:4.2.0-132026-07-29redhat
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-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

(6 across 5 ecosystems)
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
com.fasterxml.jackson.core:jackson-databind2.19.0 ... 2.21.3 (13 versions)
  • 2.10.0 up to 2.18.8: fixed in 2.18.8
  • 2.19.0 up to 2.21.4: fixed in 2.21.4
  • 3.0.0 up to 3.1.4: fixed in 3.1.4
—
tools.jackson.core:jackson-databind3.0.0 ... 3.1.3 (10 versions)
  • 3.0.0 up to 3.1.4: fixed in 3.1.4
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind2.12.1-1 ... 2.14.0-1 (10 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind2.14.0+ds-1, 2.14.0+ds-2, 2.14.0-1, 2.14.0-1+deb12u1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind2.14.0+ds-1, 2.14.0+ds-1+deb13u1, 2.14.0+ds-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind2.14.0+ds-1, 2.14.0+ds-2
  • every version on: no fix on record
—

Weakness Classification(1)

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

Additional Vendor Advisories

(7)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 39× 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.

Showing the most recent 100 of 246 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-03 14:26 UTCEPSS rescore
  3. 2026-10-02 17:56 UTCEPSS rescore
  4. 2026-10-01 19:50 UTCEPSS rescore
  5. 2026-09-30 15:03 UTCEPSS rescore
  6. 2026-09-29 15:22 UTCEPSS rescore
  7. 2026-09-28 13:51 UTCEPSS rescore
  8. 2026-09-27 13:48 UTCEPSS rescore
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-24 14:04 UTCEPSS rescore
  11. 2026-09-23 17:54 UTCEPSS rescore
  12. 2026-09-23 11:58 UTCEG score recompute
  13. 2026-09-23 11:58 UTCVendor advisory
  14. 2026-09-20 20:16 UTCEPSS rescore
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-18 10:23 UTCEG score recompute
  17. 2026-09-18 10:23 UTCVendor advisory
  18. 2026-09-17 19:31 UTCEPSS rescore
  19. 2026-09-16 14:08 UTCEPSS rescore
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-15 03:11 UTCEPSS rescore
  22. 2026-09-14 13:38 UTCEG score recompute
  23. 2026-09-14 13:38 UTCVendor advisory
  24. 2026-09-14 12:34 UTCEG score recompute
  25. 2026-09-14 12:34 UTCVendor advisory
Show 75 more
  1. 2026-09-14 02:05 UTCEG score recompute
  2. 2026-09-14 02:05 UTCVendor advisory
  3. 2026-09-13 16:47 UTCEPSS rescore
  4. 2026-09-13 12:21 UTCEG score recompute
  5. 2026-09-13 12:21 UTCVendor advisory
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 13:24 UTCEG score recompute
  8. 2026-09-11 13:24 UTCVendor advisory
  9. 2026-09-11 12:20 UTCEG score recompute
  10. 2026-09-11 12:20 UTCVendor advisory
  11. 2026-09-10 09:35 UTCEPSS rescore
  12. 2026-09-08 22:01 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-02 14:12 UTCEPSS rescore
  17. 2026-09-02 13:37 UTCEG score recompute
  18. 2026-09-02 13:37 UTCVendor advisory
  19. 2026-09-02 12:36 UTCEG score recompute
  20. 2026-09-02 12:36 UTCVendor advisory
  21. 2026-09-01 13:54 UTCEPSS rescore
  22. 2026-09-01 12:18 UTCEG score recompute
  23. 2026-09-01 12:18 UTCVendor advisory
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-08-30 20:25 UTCEG score recompute
  26. 2026-08-30 20:25 UTCVendor advisory
  27. 2026-08-30 19:17 UTCEPSS rescore
  28. 2026-08-30 01:22 UTCEPSS rescore
  29. 2026-08-28 21:41 UTCEPSS rescore
  30. 2026-08-27 14:25 UTCEPSS rescore
  31. 2026-08-26 16:22 UTCEG score recompute
  32. 2026-08-26 16:22 UTCVendor advisory
  33. 2026-08-26 14:46 UTCEPSS rescore
  34. 2026-08-26 12:19 UTCEG score recompute
  35. 2026-08-26 12:19 UTCVendor advisory
  36. 2026-08-25 13:49 UTCEPSS rescore
  37. 2026-08-25 12:18 UTCEG score recompute
  38. 2026-08-25 12:18 UTCVendor advisory
  39. 2026-08-24 22:05 UTCEG score recompute
  40. 2026-08-24 22:05 UTCVendor advisory
  41. 2026-08-24 04:43 UTCVendor advisory
  42. 2026-08-23 15:17 UTCVendor advisory
  43. 2026-08-23 02:40 UTCEG score recompute
  44. 2026-08-23 02:40 UTCVendor advisory
  45. 2026-08-23 00:19 UTCEPSS rescore
  46. 2026-08-22 13:44 UTCEG score recompute
  47. 2026-08-22 13:44 UTCVendor advisory
  48. 2026-08-21 23:49 UTCEPSS rescore
  49. 2026-08-21 22:05 UTCVendor advisory
  50. 2026-08-21 09:19 UTCEG score recompute
  51. 2026-08-21 09:19 UTCVendor advisory
  52. 2026-08-20 22:55 UTCEPSS rescore
  53. 2026-08-20 20:22 UTCVendor advisory
  54. 2026-08-20 07:45 UTCEG score recompute
  55. 2026-08-20 07:45 UTCVendor advisory
  56. 2026-08-19 17:04 UTCEPSS rescore
  57. 2026-08-19 04:48 UTCEG score recompute
  58. 2026-08-19 04:48 UTCVendor advisory
  59. 2026-08-18 13:48 UTCEPSS rescore
  60. 2026-08-17 17:06 UTCEG score recompute
  61. 2026-08-17 17:06 UTCVendor advisory
  62. 2026-08-17 13:47 UTCEPSS rescore
  63. 2026-08-17 04:29 UTCVendor advisory
  64. 2026-08-16 15:52 UTCEG score recompute
  65. 2026-08-16 15:52 UTCVendor advisory
  66. 2026-08-16 14:56 UTCEPSS rescore
  67. 2026-08-16 03:16 UTCEG score recompute
  68. 2026-08-16 03:16 UTCVendor advisory
  69. 2026-08-16 02:14 UTCEPSS rescore
  70. 2026-08-15 14:39 UTCVendor advisory
  71. 2026-08-15 02:02 UTCEG score recompute
  72. 2026-08-15 02:02 UTCVendor advisory
  73. 2026-08-15 01:30 UTCEPSS rescore
  74. 2026-08-14 13:26 UTCEG score recompute
  75. 2026-08-14 13:26 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

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 on June 23, 2026, with the most recent update on September 14, 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.2% probability of exploitation in the next 30 days (67th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54513?
CVE-2026-54513 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54513?
A fix for CVE-2026-54513 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54513 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs