Allocation of Resources Without Limits or Throttling Affecting org.springframework.retry:spring-retry package, versions [, 2.0.13)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-ORGSPRINGFRAMEWORKRETRY-17260993
- published9 Jun 2026
- disclosed8 Jun 2026
- creditUnknown
Introduced: 8 Jun 2026
CVE-2026-41710 (opens in a new tab)How to fix?
Upgrade org.springframework.retry:spring-retry to version 2.0.13 or higher.
Overview
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the stateful retry cache. An attacker can cause denial of service by generating a large number of unique failing requests that create persistent entries in the application-wide stateful retry cache. Because failed entries remain cached until a successful retry or retry exhaustion occurs, the cache can be filled with attacker-controlled entries, eventually preventing any further cache updates and causing subsequent stateful retries and circuit breakers to fail.
Note:
This is only exploitable if the application enables stateful retries using
@Retryable(stateful=true), uses attacker-controlled inputs as retry cache keys, and allows attackers to trigger failures while ensuring requests are not retried to completion.Stateless retries, which are the default behavior, are not affected.