CVE-2026-41851

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

Applications which accept user-supplied Spring Expression Language (SpEL) expressions may be vulnerable to a Denial of Service (DoS) attack if the evaluation of a SpEL expression triggers unbounded cache growth.

Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.0 through 5.3.48.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
28.5%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
No patch confirmed yet.
generic

CVE-2026-41851: Spring Framework Denial of Service via Unbounded Cache in SpEL

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

Vendor Advisories for CVE-2026-41851(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 52× 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.

  1. 2026-07-24 14:17 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:11 UTCEG score recompute 2.20
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:24 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-15 20:21 UTCGHSA enrichment
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-14 02:33 UTCGHSA enrichment
  15. 2026-07-13 22:30 UTCEPSS rescore
  16. 2026-07-13 06:13 UTCEPSS rescore
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-12 05:46 UTCEPSS rescore
  19. 2026-07-11 19:16 UTCGHSA enrichment
  20. 2026-07-11 08:27 UTCEPSS rescore
  21. 2026-07-10 21:15 UTCGHSA enrichment
  22. 2026-07-09 19:10 UTCEPSS rescore
  23. 2026-07-09 00:15 UTCGHSA enrichment
  24. 2026-07-08 15:15 UTCEPSS rescore
  25. 2026-07-08 02:08 UTCGHSA enrichment
Show 66 more
  1. 2026-07-07 13:46 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-05 15:54 UTCGHSA enrichment
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 14:30 UTCGHSA enrichment
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-03 10:15 UTCGHSA enrichment
  9. 2026-07-02 12:16 UTCGHSA enrichment
  10. 2026-07-01 15:06 UTCEPSS rescore
  11. 2026-07-01 14:17 UTCGHSA enrichment
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-30 16:18 UTCGHSA enrichment
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCGHSA enrichment
  16. 2026-06-28 16:08 UTCGHSA enrichment
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-27 21:42 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  20. 2026-06-27 21:09 UTCMITRE cvelistV5CVSS v3 → 5.3 · severity → MEDIUM
  21. 2026-06-27 18:11 UTCGHSA enrichment
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-26 20:14 UTCGHSA enrichment
  24. 2026-06-25 22:17 UTCGHSA enrichment
  25. 2026-06-25 13:49 UTCEPSS rescore
  26. 2026-06-25 13:49 UTCEPSS rescore
  27. 2026-06-25 00:18 UTCGHSA enrichment
  28. 2026-06-24 14:05 UTCEPSS rescore
  29. 2026-06-24 02:14 UTCGHSA enrichment
  30. 2026-06-23 21:33 UTCEPSS rescore
  31. 2026-06-23 04:15 UTCGHSA enrichment
  32. 2026-06-22 14:25 UTCEPSS rescore
  33. 2026-06-22 14:25 UTCEPSS rescore
  34. 2026-06-22 05:26 UTCGHSA enrichment
  35. 2026-06-21 14:56 UTCEPSS rescore
  36. 2026-06-21 14:56 UTCEPSS rescore
  37. 2026-06-21 05:57 UTCGHSA enrichment
  38. 2026-06-21 01:59 UTCEPSS rescore
  39. 2026-06-20 07:49 UTCGHSA enrichment
  40. 2026-06-19 19:25 UTCEPSS rescore
  41. 2026-06-19 09:47 UTCGHSA enrichment
  42. 2026-06-18 17:52 UTCEPSS rescore
  43. 2026-06-18 17:52 UTCEPSS rescore
  44. 2026-06-18 09:40 UTCGHSA enrichment
  45. 2026-06-17 17:53 UTCEPSS rescore
  46. 2026-06-17 10:35 UTCGHSA enrichment
  47. 2026-06-16 17:52 UTCEPSS rescore
  48. 2026-06-16 12:31 UTCGHSA enrichment
  49. 2026-06-15 17:49 UTCEPSS rescore
  50. 2026-06-15 14:30 UTCGHSA enrichment
  51. 2026-06-14 16:32 UTCGHSA enrichment
  52. 2026-06-13 23:00 UTCEPSS rescore
  53. 2026-06-13 18:34 UTCGHSA enrichment
  54. 2026-06-12 23:12 UTCEPSS rescore
  55. 2026-06-12 23:12 UTCEPSS rescore
  56. 2026-06-12 20:34 UTCGHSA enrichment
  57. 2026-06-11 22:37 UTCGHSA enrichment
  58. 2026-06-11 14:00 UTCEPSS rescore
  59. 2026-06-11 00:40 UTCGHSA enrichment
  60. 2026-06-10 22:18 UTCEPSS rescore
  61. 2026-06-10 13:22 UTCEPSS rescore
  62. 2026-06-10 13:22 UTCEPSS rescore
  63. 2026-06-10 02:43 UTCGHSA enrichment
  64. 2026-06-09 21:17 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  65. 2026-06-09 04:46 UTCEG score recompute
  66. 2026-06-09 04:45 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-41851?
CVE-2026-41851 is a high vulnerability published on June 9, 2026. Applications which accept user-supplied Spring Expression Language (SpEL) expressions may be vulnerable to a Denial of Service (DoS) attack if the evaluation of a SpEL expression triggers unbounded cache growth. Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0…
When was CVE-2026-41851 disclosed?
CVE-2026-41851 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41851 actively exploited?
CVE-2026-41851 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41851?
CVE-2026-41851 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-41851?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41851, 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-41851

Explore →

Is Your Infrastructure Affected by CVE-2026-41851?

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