Resource exhaustion in Broadcom Spring Retry
CVE-2026-41710
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.9 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS: 0.004 (28.0th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 28th percentile — 28.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.003 · newest: 0.004 · change: +0.001
Affected products
- Broadcom Spring Retry
- Spring Retry — versions 2.0.0, 1.3.0
Weakness classification (CWE)
Public proof-of-concept exploits
References
- spring.io/security/cve-2026-41710 (Vendor Advisory)
Frequently asked questions
- What is CVE-2026-41710?
- CVE-2026-41710 is a medium-severity vulnerability in Broadcom Spring Retry, classified under Allocation of Resources Without Limits or Throttling. CVSS score: 5.9/10. Published 2026-06-09.
- How severe is CVE-2026-41710?
- Medium severity. CVSS v3 base score is 5.9 out of 10.
- Is CVE-2026-41710 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.