Score 5.9 from GitHub Security Advisory published 2026-06-09. a secondary CVSS source baseline 5.9; sources differ by 0.0.
A fix is available — apply it.
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.
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).
June 9, 2026
September 4, 2026
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| org.springframework.retry:spring-retry | 1.0.0.RELEASE ... 1.3.4 (21 versions) |
| — |
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
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 184 total refreshes for this CVE.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41710
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.