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.4%, top 63% 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.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 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)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

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
Severity53% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
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.

Affected Packages

(4 across 3 ecosystems)
Maven(2)
PackageVulnerable rangeFixed inDependents
com.fasterxml.jackson.core:jackson-databind2.21.0, 2.21.1, 2.21.2, 2.21.33.1.4—
tools.jackson.core:jackson-databind3.0.0 ... 3.1.3 (10 versions)3.1.4—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
jackson-databind2.14.0+ds-1, 2.14.0+ds-1+deb13u1, 2.14.0+ds-2——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
jackson-databind2.14.0+ds-1, 2.14.0+ds-2——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 47× 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-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 22:05 UTCEG score recompute
  3. 2026-08-23 14:36 UTCEG score recompute
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-22 13:44 UTCEG score recompute
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 08:36 UTCEG score recompute
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 07:45 UTCEG score recompute
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-19 04:47 UTCEG score recompute
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 02:44 UTCEG score recompute
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-16 01:53 UTCEG score recompute
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 00:11 UTCEG score recompute
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-12 23:20 UTCEG score recompute
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-11 22:29 UTCEG score recompute
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-09 20:48 UTCEG score recompute
Show 71 more
  1. 2026-08-09 13:46 UTCEPSS rescore
  2. 2026-08-08 19:58 UTCEG score recompute
  3. 2026-08-08 16:37 UTCEPSS rescore
  4. 2026-08-07 19:07 UTCEG score recompute
  5. 2026-08-06 18:16 UTCEG score recompute
  6. 2026-08-06 13:47 UTCEPSS rescore
  7. 2026-08-05 19:17 UTCEPSS rescore
  8. 2026-08-04 15:14 UTCEG score recompute
  9. 2026-08-04 15:10 UTCEPSS rescore
  10. 2026-08-04 10:39 UTCEPSS rescore
  11. 2026-08-03 10:36 UTCEPSS rescore
  12. 2026-08-02 05:33 UTCEG score recompute
  13. 2026-08-02 02:27 UTCEPSS rescore
  14. 2026-08-01 04:42 UTCEG score recompute
  15. 2026-08-01 04:16 UTCEPSS rescore
  16. 2026-07-31 03:38 UTCEG score recompute
  17. 2026-07-30 16:28 UTCEPSS rescore
  18. 2026-07-30 02:34 UTCEG score recompute
  19. 2026-07-30 01:30 UTCEPSS rescore
  20. 2026-07-29 01:15 UTCEG score recompute
  21. 2026-07-28 15:37 UTCEPSS rescore
  22. 2026-07-27 17:45 UTCEG score recompute
  23. 2026-07-26 15:51 UTCEG score recompute
  24. 2026-07-26 14:54 UTCEPSS rescore
  25. 2026-07-25 14:18 UTCEPSS rescore
  26. 2026-07-24 14:18 UTCEPSS rescore
  27. 2026-07-23 14:18 UTCEPSS rescore
  28. 2026-07-23 03:19 UTCEG score recompute
  29. 2026-07-22 14:08 UTCEPSS rescore
  30. 2026-07-21 15:25 UTCEPSS rescore
  31. 2026-07-20 17:08 UTCEPSS rescore
  32. 2026-07-19 14:31 UTCEPSS rescore
  33. 2026-07-19 14:31 UTCEPSS rescore
  34. 2026-07-19 02:29 UTCEPSS rescore
  35. 2026-07-18 10:04 UTCEPSS rescore
  36. 2026-07-16 17:03 UTCEPSS rescore
  37. 2026-07-15 16:57 UTCEPSS rescore
  38. 2026-07-15 16:57 UTCEPSS rescore
  39. 2026-07-15 02:00 UTCEPSS rescore
  40. 2026-07-15 02:00 UTCEPSS rescore
  41. 2026-07-13 22:31 UTCEPSS rescore
  42. 2026-07-13 06:13 UTCEPSS rescore
  43. 2026-07-13 06:13 UTCEPSS rescore
  44. 2026-07-12 05:46 UTCEPSS rescore
  45. 2026-07-11 08:27 UTCEPSS rescore
  46. 2026-07-11 08:27 UTCEPSS rescore
  47. 2026-07-09 19:10 UTCEPSS rescore
  48. 2026-07-09 19:10 UTCEPSS rescore
  49. 2026-07-08 15:16 UTCEPSS rescore
  50. 2026-07-08 15:16 UTCEPSS rescore
  51. 2026-07-07 13:46 UTCEPSS rescore
  52. 2026-07-07 13:46 UTCEPSS rescore
  53. 2026-07-06 16:27 UTCEPSS rescore
  54. 2026-07-06 16:27 UTCEPSS rescore
  55. 2026-07-06 02:23 UTCEPSS rescore
  56. 2026-07-06 02:23 UTCEPSS rescore
  57. 2026-07-05 02:31 UTCEPSS rescore
  58. 2026-07-05 02:30 UTCEPSS rescore
  59. 2026-07-04 06:31 UTCEPSS rescore
  60. 2026-07-04 06:31 UTCEPSS rescore
  61. 2026-07-01 15:07 UTCEPSS rescore
  62. 2026-06-30 23:22 UTCEPSS rescore
  63. 2026-06-29 14:06 UTCEPSS rescore
  64. 2026-06-29 14:06 UTCEPSS rescore
  65. 2026-06-28 14:07 UTCEPSS rescore
  66. 2026-06-28 04:56 UTCEPSS rescore
  67. 2026-06-28 04:56 UTCEPSS rescore
  68. 2026-06-27 03:08 UTCEPSS rescore
  69. 2026-06-25 13:49 UTCEPSS rescore
  70. 2026-06-24 14:05 UTCEPSS rescore
  71. 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 0% probability of exploitation in the next 30 days, which ranks it in the top 62.8% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs