CVE-2026-41710

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory published 2026-06-09. a secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.9Exploit: NoneExposed: 0

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

An attacker can craft a large number of unique requests that trigger a failure, exhausting the capacity of the application-wide stateful retry cache. Once the cache is full, it permanently rejects any further updates, causing all later stateful retries and circuit breakers in the application to fail.

Affected versions: Spring Retry 2.0.0 through 2.0.12; 1.3.0 through 1.3.4.

CVSS v3
5.9
EG Score
5.9(high)
EPSS
19.8%
KEV
Not listed

Published

June 9, 2026

Last Modified

June 23, 2026

Advisory Details (1)

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

CVE-2026-41710: Cache Exhaustion in Stateful Retries leads to Denial of Service

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

Vendor Advisories for CVE-2026-41710(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 20× in last 7d / 90× 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-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 15:54 UTCEG score recompute
  6. 2026-07-05 15:54 UTCGHSA enrichment
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 14:59 UTCEG score recompute
  9. 2026-07-04 14:59 UTCGHSA enrichment
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-03 16:02 UTCEG score recompute
  12. 2026-07-03 16:01 UTCGHSA enrichment
  13. 2026-07-02 14:14 UTCEG score recompute
  14. 2026-07-02 14:14 UTCGHSA enrichment
  15. 2026-07-01 15:18 UTCEG score recompute
  16. 2026-07-01 15:18 UTCGHSA enrichment
  17. 2026-07-01 15:06 UTCEPSS rescore
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-30 16:19 UTCEG score recompute
  20. 2026-06-30 16:19 UTCGHSA enrichment
  21. 2026-06-29 16:35 UTCEG score recompute
  22. 2026-06-29 16:34 UTCGHSA enrichment
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-28 17:38 UTCEG score recompute
  25. 2026-06-28 17:38 UTCGHSA enrichment
Show 65 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-27 18:41 UTCEG score recompute
  4. 2026-06-27 18:41 UTCGHSA enrichment
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-26 19:44 UTCEG score recompute
  7. 2026-06-26 19:44 UTCGHSA enrichment
  8. 2026-06-25 20:47 UTCEG score recompute
  9. 2026-06-25 20:47 UTCGHSA enrichment
  10. 2026-06-25 13:49 UTCEPSS rescore
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-24 21:50 UTCEG score recompute
  13. 2026-06-24 21:50 UTCGHSA enrichment
  14. 2026-06-24 14:05 UTCEPSS rescore
  15. 2026-06-23 22:53 UTCEG score recompute
  16. 2026-06-23 22:53 UTCGHSA enrichment
  17. 2026-06-23 21:33 UTCEPSS rescore
  18. 2026-06-22 22:32 UTCEG score recompute
  19. 2026-06-22 22:32 UTCGHSA enrichment
  20. 2026-06-22 14:25 UTCEPSS rescore
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-21 19:36 UTCEG score recompute
  23. 2026-06-21 19:35 UTCGHSA enrichment
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 14:56 UTCEPSS rescore
  26. 2026-06-21 01:59 UTCEPSS rescore
  27. 2026-06-20 17:34 UTCEG score recompute
  28. 2026-06-20 17:34 UTCGHSA enrichment
  29. 2026-06-19 19:25 UTCEPSS rescore
  30. 2026-06-19 18:34 UTCEG score recompute
  31. 2026-06-19 18:34 UTCGHSA enrichment
  32. 2026-06-18 19:25 UTCEG score recompute
  33. 2026-06-18 19:25 UTCGHSA enrichment
  34. 2026-06-18 17:52 UTCEPSS rescore
  35. 2026-06-18 17:52 UTCEPSS rescore
  36. 2026-06-17 19:17 UTCEG score recompute
  37. 2026-06-17 19:17 UTCGHSA enrichment
  38. 2026-06-17 17:53 UTCEPSS rescore
  39. 2026-06-16 20:20 UTCEG score recompute
  40. 2026-06-16 20:20 UTCGHSA enrichment
  41. 2026-06-16 17:52 UTCEPSS rescore
  42. 2026-06-15 21:23 UTCEG score recompute
  43. 2026-06-15 21:23 UTCGHSA enrichment
  44. 2026-06-15 17:49 UTCEPSS rescore
  45. 2026-06-14 22:27 UTCEG score recompute
  46. 2026-06-14 22:27 UTCGHSA enrichment
  47. 2026-06-13 23:29 UTCEG score recompute
  48. 2026-06-13 23:29 UTCGHSA enrichment
  49. 2026-06-13 23:00 UTCEPSS rescore
  50. 2026-06-13 00:33 UTCEG score recompute
  51. 2026-06-13 00:33 UTCGHSA enrichment
  52. 2026-06-12 23:12 UTCEPSS rescore
  53. 2026-06-12 23:12 UTCEPSS rescore
  54. 2026-06-12 01:37 UTCEG score recompute
  55. 2026-06-12 01:37 UTCGHSA enrichment
  56. 2026-06-11 14:00 UTCEPSS rescore
  57. 2026-06-11 02:40 UTCEG score recompute
  58. 2026-06-11 02:40 UTCGHSA enrichment
  59. 2026-06-10 22:18 UTCEPSS rescore
  60. 2026-06-10 13:22 UTCEPSS rescore
  61. 2026-06-10 13:22 UTCEPSS rescore
  62. 2026-06-10 03:43 UTCEG score recompute
  63. 2026-06-10 03:43 UTCGHSA enrichment
  64. 2026-06-09 04:47 UTCEG score recompute
  65. 2026-06-09 04:45 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-41710?
CVE-2026-41710 is a medium vulnerability published on June 9, 2026. An attacker can craft a large number of unique requests that trigger a failure, exhausting the capacity of the application-wide stateful retry cache. Once the cache is full, it permanently rejects any further updates, causing all later stateful retries and circuit breakers in the application to…
When was CVE-2026-41710 disclosed?
CVE-2026-41710 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on June 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-41710 actively exploited?
CVE-2026-41710 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41710?
CVE-2026-41710 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-41710?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41710, 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-41710

Explore →

Is Your Infrastructure Affected by CVE-2026-41710?

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

Start Free Scan →Browse All CVEs