Skip to content
major vulnerability· requires attention

Widely-used Jackson databind library; high-severity deserialization flaw enabling RCE; affects many Java apps.

Applications

CVE-2026-54512

8.1
High
EPSS 0.87%Patch availableJun 24, 2026

Deserialization bypass in Jackson Databind enables RCE via attacker-controlled type.

common questions

Is CVE-2026-54512 being exploited?

Not confirmed. CVE-2026-54512 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.87% probability of exploitation in the next 30 days.

How severe is CVE-2026-54512?

CVE-2026-54512 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-54512?

Yes. A fix has been recorded for CVE-2026-54512. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-54512 affect?

CVE-2026-54512 affects jackson-databind (2.10.0–2.18.8, 2.21.4, 3.1.4). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-54512?

Upgrade to latest non-vulnerable Jackson Databind (2.18.8+, 2.21.4, or 3.1.4+)

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
jackson-databind (2.10.0–2.18.8, 2.21.4, 3.1.4)
impact

RCE via deserialization of attacker-controlled JSON; bypasses PTV allow-list to load a malicious class.

action required

Patch when possible

affected versions
FasterXML jackson-databind
  • affected>= 2.10.0 and < 2.18.8
  • affected>= 2.19.0 and < 2.21.4
  • affected>= 3.0.0 and < 3.1.4

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free