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

> Crafted calls cause denial of service in Spring Cloud Sleuth when Spring TX instrumentation is enabled.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-26m2-9g2q-v45q

## What is CVE-2026-41708?

CVE-2026-41708 is a high-severity denial of service vulnerability in Spring Cloud Sleuth, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-41708?

2 open source packages ship an affected version, including org.springframework.cloud:spring-cloud-sleuth-instrumentation. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.cloud:spring-cloud-sleuth-instrumentation` | Maven | From 3.1.0 to 3.1.11 | None |
| `org.springframework.cloud:spring-cloud-sleuth-instrumentation` | Maven | From 3.1.0 to 3.1.11 | None |

Products: Broadcom Spring Cloud Sleuth.

## How do I fix CVE-2026-41708?

No fix has been published for CVE-2026-41708 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41708 being exploited?

There is no known exploitation of CVE-2026-41708 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41708 and fix it if it is affected.

What it is: CVE-2026-41708 is a high-severity denial of service vulnerability in Spring Cloud Sleuth, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41708 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework.cloud:spring-cloud-sleuth-instrumentation (Maven): affected from 3.1.0 up to 3.1.11; no fix listed
- org.springframework.cloud:spring-cloud-sleuth-instrumentation (Maven): affected from 3.1.0 up to 3.1.11; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41708/ (Markdown: https://insights.sbomify.com/CVE-2026-41708/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41708
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41708
- OSV: https://osv.dev/vulnerability/CVE-2026-41708

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41708/
Summaries are generated and may contain mistakes; the official description above is the record.