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
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% 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).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 44(Track)EG Risk 44/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 computedSeverity65% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 24%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 15, 2026
Advisory Details (4)
Auto-updated Jul 15, 2026`@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-8qr5`@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/5974commit c7c678360624 (FasterXML/jackson-databind)
Fix landed in FasterXML/jackson-databind commit c7c678360624 — awaiting tagged release
https://github.com/FasterXML/jackson-databind/commit/c7c678360624da5bc7eed2152789fa522880db9dcommit baa2cdf5ca2b (FasterXML/jackson-databind)
Fix landed in FasterXML/jackson-databind commit baa2cdf5ca2b — awaiting tagged release
https://github.com/FasterXML/jackson-databind/commit/baa2cdf5ca2b2717fbb88d91955d69d8651df3e4Vendor Advisories for CVE-2026-59888(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:66545Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat AMQ Broker 7.13.6 release and security update
- RHSA-2026:62260Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.30.0 Release.
- RHSA-2026:54440Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Lightspeed (formerly Insights) for Runtimes security update
- GHSA-3pjw-73gf-8qr5GitHub Security AdvisoriesMedium
jackson-databind: @JsonIgnore on a Record property is bypassed with a PropertyNamingStrategy
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | jackson-databind | 2026-09-10 | redhat |
| redhat | devspaces/server-rhel9:1787757597 | 2026-09-01 | redhat |
| redhat | rh-lightspeed-runtimes/runtimes-agent-init-rhel9:1786378722 | 2026-08-12 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(2 across 1 ecosystem)
Maven(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| com.fasterxml.jackson.core:jackson-databind | 2.19.0 ... 2.21.3 (13 versions) | 2.21.4 | — |
| tools.jackson.core:jackson-databind | 3.0.0 ... 3.1.3 (10 versions) | 3.1.4 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 55× 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.
Showing the most recent 100 of 131 total refreshes for this CVE.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 04:53 UTCEG score recompute
- 2026-09-18 04:53 UTCVendor advisory
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-14 07:15 UTCEG score recompute
- 2026-09-14 07:15 UTCVendor advisory
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 07:53 UTCEG score recompute
- 2026-09-13 07:53 UTCVendor advisory
- 2026-09-12 01:45 UTCEG score recompute
- 2026-09-12 01:45 UTCVendor advisory
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 01:44 UTCEG score recompute
- 2026-09-08 01:44 UTCVendor advisory
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 21:17 UTCEG score recompute
- 2026-09-05 21:17 UTCVendor advisory
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 05:38 UTCEG score recompute
- 2026-08-31 05:38 UTCVendor advisory
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 05:19 UTCEG score recompute
- 2026-08-30 05:19 UTCVendor advisory
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 02:01 UTCEG score recompute
- 2026-08-28 02:01 UTCVendor advisory
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 01:08 UTCEG score recompute
- 2026-08-27 01:08 UTCVendor advisory
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 01:43 UTCEG score recompute
- 2026-08-26 01:43 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 21:43 UTCEG score recompute
- 2026-08-24 21:43 UTCVendor advisory
- 2026-08-23 22:17 UTCEG score recompute
- 2026-08-23 22:17 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 22:41 UTCEG score recompute
- 2026-08-22 22:41 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 23:19 UTCVendor advisory
- 2026-08-20 23:54 UTCEG score recompute
- 2026-08-20 23:54 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 00:32 UTCEG score recompute
- 2026-08-20 00:32 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 22:52 UTCEG score recompute
- 2026-08-18 22:52 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 23:21 UTCEG score recompute
- 2026-08-17 23:21 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 23:58 UTCEG score recompute
- 2026-08-16 23:58 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-16 00:35 UTCEG score recompute
- 2026-08-16 00:35 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-15 01:12 UTCVendor advisory
- 2026-08-14 01:49 UTCEG score recompute
- 2026-08-14 01:49 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 02:27 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 03:05 UTCEG score recompute
- 2026-08-11 03:42 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 04:19 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 04:57 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 05:35 UTCEG score recompute
- 2026-08-07 06:12 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 06:50 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 07:28 UTCEG score recompute
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 08:00 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 09:04 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 09:42 UTCEG score recompute
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 10:20 UTCEG score recompute
- 2026-07-30 16:28 UTCEPSS rescore
Frequently asked(5)
What is CVE-2026-59888?
When was CVE-2026-59888 disclosed?
Is CVE-2026-59888 actively exploited?
What is the CVSS score of CVE-2026-59888?
How do I remediate CVE-2026-59888?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by 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.