Stateful retry interruption via cache exhaustion
Published Jun 9, 2026 · Updated Jun 9, 2026
Resource exhaustion in Spring Retry 1.3.0 through 1.3.4 and 2.0.0 through 2.0.12 allows remote attackers to interrupt retries. The RetryContextCache capacity check rejects every update after the cache reaches its limit, while abandoned failed contexts remain cached. Exploitation requires stateful retries, attacker-controlled keys, triggerable failures, and requests that are never resubmitted; stateless retries are unaffected, and disruption is limited to stateful retries and circuit breakers.
Summary
What happened
Resource exhaustion in Spring Retry 1.3.0 through 1.3.4 and 2.0.0 through 2.0.12 allows remote attackers to interrupt retries. The RetryContextCache capacity check rejects every update after the cache reaches its limit, while abandoned failed contexts remain cached. Exploitation requires stateful retries, attacker-controlled keys, triggerable failures, and requests that are never resubmitted; stateless retries are unaffected, and disruption is limited to stateful retries and circuit breakers.
The record
- CVE
- CVE-2026-41710
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- Spring
- Product
- Spring Retry
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2026CVE publishedPublication date reported by the CVE source.
- Jun 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.3.0 <1.3.5
- Affected versionversion=2.0.0 <2.0.13
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo