Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Timing attack in Spring Boot DevTools remote secret comparison

IdentifiersCVE-2026-40972CWE-208· Observable Timing Discrepancy

CVE-2026-40972 is a timing side-channel vulnerability in Spring Boot DevTools remote access. The flaw is in the spring-boot-devtools module, specifically the org.springframework.boot.devtools.remote.server.HttpHeaderAccessManager class, where the configured DevTools remote secret was compared against an attacker-supplied HTTP header using Java's non-constant-time String.equals(). Because String.equals() short-circuits on the first mismatched character, it leaks timing differences that can allow an adjacent-network attacker to infer the secret incrementally, character by character. If the attacker successfully reconstructs the remote secret, they can authenticate to the DevTools remote endpoint and use the live reload mechanism to upload changed class files. Affected versions are Spring Boot 4.0.0 through 4.0.5, 3.5.0 through 3.5.13, 3.4.0 through 3.4.15, 3.3.0 through 3.3.18, and 2.7.0 through 2.7.32; unsupported versions are also affected per the vendor advisory. The issue was fixed by replacing String.equals() with MessageDigest.isEqual(), storing the expected secret as a UTF-8 byte array, and adding a null check before converting the provided secret to bytes.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow an attacker on the same network segment or similarly low-latency adjacent network position to recover the configured Spring Boot DevTools remote secret without prior authentication. Once the secret is known, the attacker can authenticate as a legitimate DevTools remote client and upload malicious or modified class files through the DevTools live reload mechanism, resulting in remote code execution in the target application. This can lead to full compromise of confidentiality, integrity, and availability of the affected application and potentially the underlying host or connected systems.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, disable Spring Boot DevTools remote functionality, especially in production or any environment reachable from untrusted or semi-trusted networks. Ensure spring.devtools.remote.secret is not configured unless remote DevTools access is explicitly required. Restrict network access to DevTools remote endpoints so only trusted administrative hosts can reach them, and avoid exposing those endpoints across shared, adjacent, or otherwise attacker-accessible networks.

Remediation

Patch, then assume compromise.

Upgrade Spring Boot DevTools to a fixed release. Fixed versions are 4.0.6 and 3.5.14 in open source releases; 3.4.16, 3.3.19, and 2.7.33 are available through Spring Enterprise Support. Systems on unsupported branches should be upgraded to a supported fixed release. The vendor fix replaces the vulnerable non-constant-time comparison with MessageDigest.isEqual() and changes secret handling to byte-array comparison.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
BroadcomSpring Bootapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity5

Community discussion across Reddit, Mastodon, and other social sources.