CVE-2026-59888

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% 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
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

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 computed
Severity65% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 15, 2026

Advisory Details (4)

Auto-updated Jul 15, 2026
Patch 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-8qr5
github_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/5974
github_commit

commit c7c678360624 (FasterXML/jackson-databind)

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

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

commit baa2cdf5ca2b (FasterXML/jackson-databind)

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

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

Vendor Advisories for CVE-2026-59888(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrh-lightspeed-runtimes/runtimes-agent-init-rhel9:17863787222026-08-12redhat

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)
PackageVulnerable rangeFixed inDependents
com.fasterxml.jackson.core:jackson-databind2.19.0 ... 2.21.3 (13 versions)2.21.4—
tools.jackson.core:jackson-databind3.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 17× in last 7d / 69× 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 101 total refreshes for this CVE.

  1. 2026-08-30 05:19 UTCEG score recompute
  2. 2026-08-30 05:19 UTCVendor advisory
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-28 02:01 UTCEG score recompute
  6. 2026-08-28 02:01 UTCVendor advisory
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-27 01:08 UTCEG score recompute
  9. 2026-08-27 01:08 UTCVendor advisory
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-26 01:43 UTCEG score recompute
  12. 2026-08-26 01:43 UTCVendor advisory
  13. 2026-08-25 13:49 UTCEPSS rescore
  14. 2026-08-24 21:43 UTCEG score recompute
  15. 2026-08-24 21:43 UTCVendor advisory
  16. 2026-08-23 22:17 UTCEG score recompute
  17. 2026-08-23 22:17 UTCVendor advisory
  18. 2026-08-23 00:19 UTCEPSS rescore
  19. 2026-08-22 22:41 UTCEG score recompute
  20. 2026-08-22 22:41 UTCVendor advisory
  21. 2026-08-21 23:49 UTCEPSS rescore
  22. 2026-08-21 23:19 UTCVendor advisory
  23. 2026-08-20 23:54 UTCEG score recompute
  24. 2026-08-20 23:54 UTCVendor advisory
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 75 more
  1. 2026-08-20 00:32 UTCEG score recompute
  2. 2026-08-20 00:32 UTCVendor advisory
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-18 22:52 UTCEG score recompute
  5. 2026-08-18 22:52 UTCVendor advisory
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 23:21 UTCEG score recompute
  8. 2026-08-17 23:21 UTCVendor advisory
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 23:58 UTCEG score recompute
  11. 2026-08-16 23:58 UTCVendor advisory
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-16 00:35 UTCEG score recompute
  15. 2026-08-16 00:35 UTCVendor advisory
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-15 01:12 UTCVendor advisory
  18. 2026-08-14 01:49 UTCEG score recompute
  19. 2026-08-14 01:49 UTCVendor advisory
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 02:27 UTCEG score recompute
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-12 03:05 UTCEG score recompute
  24. 2026-08-11 03:42 UTCEG score recompute
  25. 2026-08-11 00:00 UTCEPSS rescore
  26. 2026-08-10 04:19 UTCEG score recompute
  27. 2026-08-09 13:46 UTCEPSS rescore
  28. 2026-08-09 04:57 UTCEG score recompute
  29. 2026-08-08 16:37 UTCEPSS rescore
  30. 2026-08-08 05:35 UTCEG score recompute
  31. 2026-08-07 06:12 UTCEG score recompute
  32. 2026-08-06 13:47 UTCEPSS rescore
  33. 2026-08-06 06:50 UTCEG score recompute
  34. 2026-08-05 19:17 UTCEPSS rescore
  35. 2026-08-05 07:28 UTCEG score recompute
  36. 2026-08-04 15:10 UTCEPSS rescore
  37. 2026-08-04 10:39 UTCEPSS rescore
  38. 2026-08-04 08:00 UTCEG score recompute
  39. 2026-08-03 10:36 UTCEPSS rescore
  40. 2026-08-02 09:04 UTCEG score recompute
  41. 2026-08-02 02:27 UTCEPSS rescore
  42. 2026-08-01 09:42 UTCEG score recompute
  43. 2026-08-01 04:16 UTCEPSS rescore
  44. 2026-07-31 10:20 UTCEG score recompute
  45. 2026-07-30 16:28 UTCEPSS rescore
  46. 2026-07-30 10:57 UTCEG score recompute
  47. 2026-07-30 01:30 UTCEPSS rescore
  48. 2026-07-30 01:30 UTCEPSS rescore
  49. 2026-07-29 11:33 UTCEG score recompute
  50. 2026-07-28 15:37 UTCEPSS rescore
  51. 2026-07-28 12:08 UTCEG score recompute
  52. 2026-07-27 14:14 UTCEPSS rescore
  53. 2026-07-27 11:08 UTCEG score recompute
  54. 2026-07-26 14:54 UTCEPSS rescore
  55. 2026-07-26 14:54 UTCEPSS rescore
  56. 2026-07-26 11:45 UTCEG score recompute
  57. 2026-07-25 14:18 UTCEPSS rescore
  58. 2026-07-25 14:18 UTCEPSS rescore
  59. 2026-07-24 14:18 UTCEPSS rescore
  60. 2026-07-24 14:18 UTCEPSS rescore
  61. 2026-07-23 14:18 UTCEPSS rescore
  62. 2026-07-23 14:18 UTCEPSS rescore
  63. 2026-07-23 03:21 UTCEG score recompute
  64. 2026-07-22 14:08 UTCEPSS rescore
  65. 2026-07-22 14:08 UTCEPSS rescore
  66. 2026-07-21 15:25 UTCEPSS rescore
  67. 2026-07-21 15:25 UTCEPSS rescore
  68. 2026-07-20 17:08 UTCEPSS rescore
  69. 2026-07-19 14:31 UTCEPSS rescore
  70. 2026-07-19 02:29 UTCEPSS rescore
  71. 2026-07-18 10:04 UTCEPSS rescore
  72. 2026-07-16 17:03 UTCEPSS rescore
  73. 2026-07-15 16:57 UTCEPSS rescore
  74. 2026-07-15 16:57 UTCEPSS rescore
  75. 2026-07-14 17:16 UTCEG score recompute

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 0% probability of exploitation in the next 30 days, which ranks it in the top 76.8% of all scored CVEs.
What is the CVSS score of CVE-2026-59888?
CVE-2026-59888 has a CVSS v3 base score of 6.5 (NVD).
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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59888

Explore →

Is Your Infrastructure Affected by CVE-2026-59888?

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

Start Free Scan →Browse All CVEs