jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.15.0 until 2.18.8, 2.21.4, and 3.1.4, Java Records using a PropertyNamingStrategy can bypass @JsonIgnore because POJOPropertiesCollector._removeUnwantedIgnorals() records an ignored component under its original implicit name before _renameUsing() applies the naming strategy, allowing the renamed JSON key to be assigned to the Record constructor parameter. This issue is fixed in versions 2.18.8, 2.21.4, and 3.1.4.
CVE-2026-59888
MEDIUMPre-NVD 6.56.5Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: secondary
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(low)
- EPSS
- 15.9%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 15, 2026
Advisory Details (4)
Auto-updated Jul 15, 2026Patch available. Sources: github_commit, github_pr, github.
github Patch Available
`@JsonIgnore` on a Record property is bypassed with a PropertyNamingStrategy in jackson-databind [CVE-2026-59888] · Advisory · FasterXML/jackson-databind · GitHub
https://github.com/FasterXML/jackson-databind/security/advisories/GHSA-3pjw-73gf-8qr5github_pr
`@JsonIgnore` on Record property ignored with `PropertyNamingStrategy` [CVE-2026-59888]
Fix merged in FasterXML/jackson-databind PR #5974 on 2026-05-07 — awaiting tagged release
https://github.com/FasterXML/jackson-databind/pull/5974github_commit
commit c7c678360624 (FasterXML/jackson-databind)
Fix landed in FasterXML/jackson-databind commit c7c678360624 — awaiting tagged release
https://github.com/FasterXML/jackson-databind/commit/c7c678360624da5bc7eed2152789fa522880db9dgithub_commit
commit baa2cdf5ca2b (FasterXML/jackson-databind)
Fix landed in FasterXML/jackson-databind commit baa2cdf5ca2b — awaiting tagged release
https://github.com/FasterXML/jackson-databind/commit/baa2cdf5ca2b2717fbb88d91955d69d8651df3e4Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× 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.
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:39 UTCEG score recompute
- 2026-07-14 17:16 UTCEG score recompute
- 2026-07-14 17:10 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-59888?
CVE-2026-59888 is a medium vulnerability published on July 14, 2026. jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.15.0 until 2.18.8, 2.21.4, and 3.1.4, Java Records using a PropertyNamingStrategy can bypass @JsonIgnore because POJOPropertiesCollector.removeUnwantedIgnorals() records an…
When was CVE-2026-59888 disclosed?
CVE-2026-59888 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59888 actively exploited?
CVE-2026-59888 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-59888?
CVE-2026-59888 has a CVSS v3 base score of 6.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-59888?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59888, 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-59888
Is Your Infrastructure Affected by CVE-2026-59888?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.