CVE-2026-41710 json
Cache Exhaustion in Stateful Retries leads to Denial of Service
published 2026-06-09 5 mo ago modified 2026-09-04 2 mo ago also GHSA-2827-2mxx-j8pv , EUVD-2026-35321
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 20%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.springframework.retry:spring-retry 2.0.13
- Spring Spring Retry 1.3.5, 2.0.12.1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-41710 updated cvss 5.9
spring-retry: Spring Retry: Denial of Service via cache exhaustion
-
Red Hat build of Apache Camel 4 for Quarkus 3 spring-retry Red Hat Data Grid 8 spring-retryaffected: workaround, no fix available “Fix deferred”
-
Red Hat Fuse 7 spring-retry Red Hat JBoss Enterprise Application Platform Expansion Pack spring-retryaffected: workaround, no fix planned “Out of support scope”
-
Red Hat OpenShift Dev Spaces devspaces/openvsx-rhel9, devspaces/pluginregistry-rhel9affected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.retry:spring-retry | >=2.0.0, <2.0.13 <=1.3.4 |
2.0.13 |
Affected products
- Spring Spring Retry
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
github.com
/spring-attic/spring-retry/commit/6f351edae3d3575fffbde3c0f62fef963dacd152
web
-
spring.io
/security/cve-2026-41710
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-41710
advisory
-
github.com
/spring-attic/spring-retry/issues/505
web
-
github.com
/spring-attic/spring-retry/releases/tag/v2.0.13
web
-
github.com
/spring-projects/spring-retry
package
Sources
- CVE List CVE-2026-41710
- GitHub Advisory GHSA-2827-2mxx-j8pv
- NVD CVE-2026-41710
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.