CVE Intelligence
Skip to main content
HIGH

CVE-2026-54513

CVE-2026-54513 — jackson-databind: Array subtype allowlist bypass in BasicPolymorphicTypeValidator (allowIfSubTypeIsArray)

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.

Published Updated Sources: cvelistV5, GitHub_M

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

1%

chance of exploitation in 30 days

Affects

fasterxml

48 products listed

CVSS base

8.1

HIGH

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (2)

fasterxmlredhat

Products (48)

jackson databindcryostat 4 on rhel 9red hat amq broker 7 13 6red hat amq broker 7 14 1red hat build of apache camel 4 18 3 for spring boot 3 5 16red hat build of apache camel 4 18 for quarkus 3 33red hat build of keycloak 26 4red hat build of keycloak 26 4 14red hat build of keycloak 26 6red hat build of keycloak 26 6 5red hat certificate system 10 8 for rhel 8red hat data grid 8 6 2red hat enterprise linux 10red hat enterprise linux 10 0 extended update supportred hat enterprise linux 8red hat enterprise linux 8 4 advanced mission critical update supportred hat enterprise linux 8 4 extended update support long life add onred hat enterprise linux 8 6 advanced mission critical update supportred hat enterprise linux 8 6 extended update support long life add onred hat enterprise linux 8 8 telecommunications update servicered hat enterprise linux 8 8 update services for sap solutionsred hat enterprise linux 9red hat enterprise linux 9 2 update services for sap solutionsred hat enterprise linux 9 4 update services for sap solutionsred hat enterprise linux 9 6 extended update supportstreams for apache kafka 3 2 1red hat openshift dev spaces 3 30openshift developer tools and servicesopenshift serverlessred hat ai inference serverred hat amq clientsred hat ansible automation platform 2red hat build of apache camel 4 for quarkus 3red hat build of apache camel hawtio 4red hat build of apicurio registry 3red hat build of debezium 3red hat build of quarkusred hat enterprise linux ai rhel ai 3red hat jboss enterprise application platform 7red hat jboss enterprise application platform 8red hat jboss enterprise application platform expansion packred hat lightspeed for runtimes operatorred hat offline knowledge portalred hat openshift ai rhoaired hat openshift dev spacesred hat satellite 6red hat single sign on 7streams for apache kafka 2

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
8.1CVSS 3.1HIGH——cvelistV5

Weakness & attack patterns

  • CWE-184

References

25 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.