Unauthenticated service interruption via crafted calls
Published Jun 15, 2026 · Updated Jun 15, 2026
Denial of service in Spring Cloud Sleuth 3.1.0 through 3.1.13 allows remote attackers to interrupt applications via crafted calls. Spring has not published which Spring TX instrumentation code path mishandles the calls or what resource becomes exhausted. Exposure requires the instrumentation artifact and enabled Spring TX instrumentation; the reported consequence is application availability loss without data disclosure or modification.
Summary
What happened
Denial of service in Spring Cloud Sleuth 3.1.0 through 3.1.13 allows remote attackers to interrupt applications via crafted calls. Spring has not published which Spring TX instrumentation code path mishandles the calls or what resource becomes exhausted. Exposure requires the instrumentation artifact and enabled Spring TX instrumentation; the reported consequence is application availability loss without data disclosure or modification.
The record
- CVE
- CVE-2026-41708
- Published
- Jun 15, 2026
- Updated
- Jun 15, 2026
- Vendor
- Spring
- Product
- Spring Cloud Sleuth
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2026CVE publishedPublication date reported by the CVE source.
- Jun 15, 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=3.1.0 <3.1.14
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.
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