CVE-2026-54516

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% 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
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: 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.21.0 until 2.21.4 and 3.1.4, POJOPropertiesCollector._renameProperties() allows a property with @JsonProperty("renamed") on the getter and @JsonIgnore on the setter to be renamed rather than dropped. With MapperFeature.INFER_PROPERTY_MUTATORS enabled (default), the private backing field is retained; during deserialization BeanDeserializerFactory.addBeanProps() sees hasField()==true, builds a FieldProperty, and makes the backing field writable. An attacker supplying the renamed JSON key writes the backing field directly, bypassing the @JsonIgnore on the setter. This vulnerability is fixed in 3.1.4.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
20.1%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 27, 2026

Advisory Details (5)

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

Renamed @JsonIgnore'd setters can deserialize via private fields in jackson-databind · Advisory · FasterXML/jackson-databind · GitHub

https://github.com/FasterXML/jackson-databind/security/advisories/GHSA-9fxm-vc8v-hj55
github_pr

Backport #5967: "Renamed `@JsonIgnore`d setters can deserialize via private fields" [CVE-2026-54516]

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

https://github.com/FasterXML/jackson-databind/pull/5968
github_pr

Renamed `@JsonIgnore`d setters can deserialize via private fields [CVE-2026-54516]

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

https://github.com/FasterXML/jackson-databind/pull/5967
github_commit

commit e88cb17006b6 (FasterXML/jackson-databind)

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

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

commit c3d56dd25d52 (FasterXML/jackson-databind)

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

https://github.com/FasterXML/jackson-databind/commit/c3d56dd25d52319828147c5b9aeabf2d485c250a

Vendor Advisories for CVE-2026-54516(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 16× in last 7d / 31× 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-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 08:06 UTCEG score recompute
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 06:57 UTCEG score recompute
  7. 2026-07-05 02:31 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-04 06:06 UTCEG score recompute
  12. 2026-07-03 05:13 UTCEG score recompute
  13. 2026-07-02 04:18 UTCEG score recompute
  14. 2026-07-01 15:07 UTCEPSS rescore
  15. 2026-07-01 03:27 UTCEG score recompute
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 02:36 UTCEG score recompute
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 01:45 UTCEG score recompute
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 00:54 UTCEG score recompute
  25. 2026-06-27 03:08 UTCEPSS rescore
Show 6 more
  1. 2026-06-27 00:03 UTCEG score recompute
  2. 2026-06-25 23:12 UTCEG score recompute
  3. 2026-06-25 13:49 UTCEPSS rescore
  4. 2026-06-24 22:21 UTCEG score recompute
  5. 2026-06-24 14:05 UTCEPSS rescore
  6. 2026-06-23 21:30 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54516?
CVE-2026-54516 is a medium vulnerability published on June 23, 2026. jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3.1.4, POJOPropertiesCollector.renameProperties() allows a property with @JsonProperty("renamed") on the getter and @JsonIgnore on the setter to be…
When was CVE-2026-54516 disclosed?
CVE-2026-54516 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on June 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54516 actively exploited?
CVE-2026-54516 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54516?
CVE-2026-54516 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-54516?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54516, 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-54516

Explore →

Is Your Infrastructure Affected by CVE-2026-54516?

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