CVE-2026-41708: In Spring Cloud Sleuth, it is possible for a user to provide specially crafted calls that may cause a denial-o

Routine

HIGH 7.5REMOTEUPGRADE

CVE-2026-41708 is a high-severity flaw (CVSS 7.5) affecting spring cloud sleuth. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 80%)
CISA exploited list	No
Weakness	CWE-400
Published	2026-06-15
Last modified	2026-10-25

Publisher (CNA): VMware · Vendor: broadcom

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-15 20:16 UTCPublished CVE record published
2026-10-25 23:10 UTCUpdated Record last modified

broadcom spring cloud sleuth UPGRADE

Affected: >= 3.1.0 and < 3.1.14

Fixed in: 3.1.14

Safe to downgrade to: a release before 3.1.0

1. Check installed version

apt-cache policy spring-cloud-sleuth || rpm -q spring-cloud-sleuth || spring-cloud-sleuth --version

2. UPGRADE to 3.1.14 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spring-cloud-sleuth

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spring-cloud-sleuth

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.1.0 (Debian / Ubuntu)

apt-cache madison spring-cloud-sleuth sudo apt install spring-cloud-sleuth=<VERSION_BEFORE_3.1.0> sudo apt-mark hold spring-cloud-sleuth

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spring-cloud-sleuth sudo dnf downgrade spring-cloud-sleuth-<VERSION_BEFORE_3.1.0> sudo dnf versionlock add spring-cloud-sleuth

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41708?

spring cloud sleuth: upgrade to 3.1.14. Exact commands for each OS are on this page.

Is CVE-2026-41708 being exploited?

CVE-2026-41708 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41708 affect?

CVE-2026-41708 affects spring cloud sleuth. Severity is high (CVSS 7.5). 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-clo

How urgent is CVE-2026-41708?

Priority 36/100. High severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs