NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2026-40972 — spring-boot-devtools

HIGH

CVE-2026-40972 is a high-severity (CVSS 7.5) CWE-208 vulnerability in org.springframework.boot:spring-boot-devtools. A fix is available for org.springframework.boot:spring-boot-devtools — see the affected versions and patch details below.

Spring Boot DevTools remote secret comparison is vulnerable to timing attacks

Also known asGHSA-56v8-86gj-66jp
Published
Updated
Affected
5 pkgs
Patched
2 / 5
Exploits
None indexed
Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-40972.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs18th percentile — riskier than 18% of all scored CVEsHighest risk
0.00%0.28%0.55%0.83%0.1%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected
☕org.springframework.boot:spring-boot-devtools☕org.springframework.boot:spring-boot-devtools☕org.springframework.boot:spring-boot-devtools☕org.springframework.boot:spring-boot-devtools☕org.springframework.boot:spring-boot-devtools

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

An attacker on the same network as the remote application may be able to utilize a timing attack to discover information about the remote secret. In extreme circumstances this could result in the attacker determining the secret and uploading changed classes, thereby achieving remote code execution in the remote application.

Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); DevTools remote secret comparison. Versions that are no longer supported are also affected per vendor advisory.

Affected Packages

5 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.springframework.boot:spring-boot-devtools≥ 4.0.0&&< 4.0.64.0.6org.springframework.boot:spring-boot-devtools:4.0.6
☕Mavenorg.springframework.boot:spring-boot-devtools≥ 3.5.0&&< 3.5.143.5.14org.springframework.boot:spring-boot-devtools:3.5.14
☕Mavenorg.springframework.boot:spring-boot-devtools≥ 3.4.0No fix
☕Mavenorg.springframework.boot:spring-boot-devtools≥ 3.3.0No fix
☕Mavenorg.springframework.boot:spring-boot-devtoolsall versionsNo fix

Affected Products

1 product · 5 configurations
Application
spring bootvmware
≥ 4.0.0 && < 4.0.6
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.boot:spring-boot-devtools, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.springframework.boot:spring-boot-devtools to 4.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-40972 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
Workaround published by Red Hat
To mitigate this issue, disable the Spring Boot DevTools remote functionality in production environments. This feature is primarily intended for development and should not be enabled in publicly accessible deployments. To disable remote DevTools, ensure the `spring.devtools.remote.secret` property is not configured, or explicitly set `spring.devtools.remote.enabled=false` in your application's `application.properties` or `application.yml` file. Example for `application.properties`: `spring.devtools.remote.enabled=false` Disabling this feature may impact development workflows that rely on remote DevTools capabilities. A restart of the application is required for the changes to take effect.
Source: Red Hat security advisory for CVE-2026-40972 (CC BY 4.0)
ProductFixed inAdvisory
HawtIO HawtIO 4.4.0spring-bootRHSA-2026:25089
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14spring-bootRHSA-2026:17668
Red Hat OpenShift Dev Spaces 3.28devspaces/openvsx-rhel9:1779528224RHSA-2026:21772

Frequently Asked Questions

An attacker on the same network as the remote application may be able to utilize a timing attack to discover information about the remote secret. In extreme circumstances this could result in the attacker determining the secret and uploading changed classes, thereby achieving remote code execution in the remote application. Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); DevTools remote secret comparison. Versions that are no longer supported are also affected per vendor advisory.
O3 Security · Impact-Aware SCA

Is CVE-2026-40972 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2026-40972: spring-boot-devtools RCE — Fixed in 4.0.6