CVE-2026-59314

LOWNVD 3.73.7
EchelonGraph scoreMEDIUM confidence

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

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-08-27. NVD baseline CVSS 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
3.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 3.7Exploit: 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.

Applications that build a Content-Disposition header value from untrusted input may be vulnerable to HTTP response splitting when the input is a malicious file name. 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
3.7
EG Score
3.7LOWmedium confidence
EG Risk
17
EG Risk 17/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)
Severity37% × 45%
The EG Score, 3.7 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
15th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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 1, 2026

References (1)

Vendor Advisories for CVE-2026-59314(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 13× in last 7d / 46× 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.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  3. 2026-10-12 15:52 UTCEG score recompute
  4. 2026-10-11 19:36 UTCEG score recompute
  5. 2026-10-11 16:51 UTCEG score recompute
  6. 2026-10-11 14:14 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  10. 2026-10-09 08:20 UTCEG score recompute
  11. 2026-10-09 08:20 UTCGHSA enrichmentGHSA-j392-mc64-q79h · GitHub severity LOW · GitHub CVSS 3.7
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  15. 2026-10-06 07:31 UTCEG score recompute
  16. 2026-10-06 07:31 UTCGHSA enrichmentGHSA-j392-mc64-q79h · GitHub severity LOW · GitHub CVSS 3.7
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  19. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  20. 2026-10-03 06:03 UTCEG score recompute
  21. 2026-10-03 06:03 UTCGHSA enrichmentGHSA-j392-mc64-q79h · GitHub severity LOW · GitHub CVSS 3.7
  22. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  23. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  25. 2026-09-30 04:57 UTCEG score recompute
Show 52 more
  1. 2026-09-30 04:57 UTCGHSA enrichmentGHSA-j392-mc64-q79h · GitHub severity LOW · GitHub CVSS 3.7
  2. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  3. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  4. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  5. 2026-09-26 18:28 UTCEG score recompute
  6. 2026-09-26 18:27 UTCGHSA enrichmentGHSA-j392-mc64-q79h · GitHub severity LOW · GitHub CVSS 3.7
  7. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  8. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  9. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-09-22 21:36 UTCEG score recompute
  11. 2026-09-22 21:36 UTCGHSA enrichmentGHSA-j392-mc64-q79h · GitHub severity LOW · GitHub CVSS 3.7
  12. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-09-19 20:48 UTCEG score recompute
  14. 2026-09-19 20:48 UTCGHSA enrichmentGHSA-j392-mc64-q79h · GitHub severity LOW · GitHub CVSS 3.7
  15. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-09-16 20:00 UTCEG score recompute
  18. 2026-09-16 20:00 UTCGHSA enrichmentGHSA-j392-mc64-q79h · GitHub severity LOW · GitHub CVSS 3.7
  19. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-09-13 19:12 UTCEG score recompute
  23. 2026-09-13 19:12 UTCGHSA enrichmentGHSA-j392-mc64-q79h · GitHub severity LOW · GitHub CVSS 3.7
  24. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  26. 2026-09-10 18:24 UTCEG score recompute
  27. 2026-09-10 18:24 UTCGHSA enrichmentGHSA-j392-mc64-q79h · GitHub severity LOW · GitHub CVSS 3.7
  28. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  29. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  30. 2026-09-07 17:34 UTCEG score recompute
  31. 2026-09-07 17:34 UTCGHSA enrichmentGHSA-j392-mc64-q79h · GitHub severity LOW · GitHub CVSS 3.7
  32. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  33. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  34. 2026-09-04 16:47 UTCEG score recompute
  35. 2026-09-04 16:47 UTCGHSA enrichmentGHSA-j392-mc64-q79h · GitHub severity LOW · GitHub CVSS 3.7
  36. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  37. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  38. 2026-09-01 15:57 UTCGHSA enrichmentGHSA-j392-mc64-q79h · GitHub severity LOW · GitHub CVSS 3.7
  39. 2026-09-01 15:13 UTCEG score recompute
  40. 2026-09-01 15:13 UTCGHSA enrichmentGHSA-j392-mc64-q79h · GitHub severity LOW · GitHub CVSS 3.7
  41. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  42. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  43. 2026-08-31 18:23 UTCEG score recomputeFirst assessed: 3.7 LOW
  44. 2026-08-31 18:23 UTCGHSA enrichmentGHSA-j392-mc64-q79h
  45. 2026-08-31 18:20 UTCNVD updateCVSS v3 → 3.7 · severity → LOW
  46. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  47. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  48. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  49. 2026-08-28 18:59 UTCGHSA enrichmentGHSA-j392-mc64-q79h
  50. 2026-08-27 20:26 UTCNVD update
  51. 2026-08-27 20:16 UTCEG score recompute
  52. 2026-08-27 20:13 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59314?
CVE-2026-59314 is a low-severity vulnerability; its CVE record was published on August 27, 2026. Applications that build a Content-Disposition header value from untrusted input may be vulnerable to HTTP response splitting when the input is a malicious file name. 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…
When was the CVE record for CVE-2026-59314 published?
The CVE record for CVE-2026-59314 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 1, 2026; the record at its source may have been updated since.
Is CVE-2026-59314 actively exploited?
CVE-2026-59314 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59314?
CVE-2026-59314 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-59314?
No fix for CVE-2026-59314 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-59314 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-59314

Explore →

Is Your Infrastructure Affected by CVE-2026-59314?

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