CVE-2026-59282

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VMware by Broadcom) lists Spring Framework versions 7.0.0 up to and including 7.0.8, 6.2.0 up to and including 6.2.19, 6.1.0 up to and including 6.1.28, 6.0.0 up to and including 6.0.30 and 2 more ranges as affected. No release containing a fix is confirmed on record.

Spring Framework applications that use Spring's data binding infrastructure to apply user-supplied property paths onto a target object may be vulnerable to a Denial of Service (DoS) attack. Spring Framework 7.0.0 - 7.0.8 Spring Framework 6.2.0 - 6.2.19 Spring Framework 6.1.0 - 6.1.28 Spring Framework 6.0.0 - 6.0.30 Spring Framework 5.3.0 - 5.3.49 Spring Framework 5.2.25.RELEASE and earlier

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 27, 2026

Last Modified

September 2, 2026

Advisory Details (1)

Auto-updated Aug 28, 2026
No fix on record yet.
Web page

Spring Framework Denial of Service via Unbounded List Growth in Data Binding

https://spring.io/security/cve-2026-59282

Vendor Advisories for CVE-2026-59282(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libspring-java4.3.30-2, 4.3.30-3, 4.3.30-4
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libspring-java4.3.30-3, 4.3.30-4
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libspring-java4.3.30-3, 4.3.30-4
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 106× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 175 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 75 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-59282?
CVE-2026-59282 is a high-severity vulnerability; its CVE record was published on August 27, 2026. Spring Framework applications that use Spring's data binding infrastructure to apply user-supplied property paths onto a target object may be vulnerable to a Denial of Service (DoS) attack. Spring Framework 7.0.0 - 7.0.8 Spring Framework 6.2.0 - 6.2.19 Spring Framework 6.1.0 - 6.1.28 Spring…
When was the CVE record for CVE-2026-59282 published?
The CVE record for CVE-2026-59282 was published on August 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 2, 2026; the record at its source may have been updated since.
Is CVE-2026-59282 actively exploited?
CVE-2026-59282 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59282?
CVE-2026-59282 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-59282?
No fix for CVE-2026-59282 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VMware by Broadcom) lists Spring Framework versions 7.0.0 up to and including 7.0.8, 6.2.0 up to and including 6.2.19, 6.1.0 up to and including 6.1.28, 6.0.0 up to and including 6.0.30 and 2 more ranges as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-59282 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59282?

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