Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-40972: An attacker on the same network as the remote application may be able to utilize a timing attack to discover i

31
Routine
HIGH 7.5UPGRADE

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

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.

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorAdjacent network
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance0.3% (top 82%)
CISA exploited listNo
WeaknessCWE-208
Published2026-04-28
Last modified2026-07-24
Publisher (CNA): VMware · Vendor: vmware

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

vmware spring boot UPGRADE
Affected: < 2.7.33 · >= 3.3.0 and < 3.3.19 · >= 3.4.0 and < 3.4.16 · >= 3.5.0 and < 3.5.14 · >= 4.0.0 and < 4.0.6
Fixed in: 2.7.33, 3.3.19, 3.4.16, 3.5.14, 4.0.6
Safe to downgrade to: a release before 3.3.0
1. Check installed version
apt-cache policy spring-boot || rpm -q spring-boot || spring-boot --version
2. UPGRADE to 2.7.33 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade spring-boot
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade spring-boot
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.3.0 (Debian / Ubuntu)
apt-cache madison spring-boot sudo apt install spring-boot=<VERSION_BEFORE_3.3.0> sudo apt-mark hold spring-boot
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list spring-boot sudo dnf downgrade spring-boot-<VERSION_BEFORE_3.3.0> sudo dnf versionlock add spring-boot
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-40972?

spring boot: upgrade to 2.7.33, 3.3.19, 3.4.16, 3.5.14, 4.0.6. Exact commands for each OS are on this page.

Is CVE-2026-40972 being exploited?

CVE-2026-40972 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-40972 affect?

CVE-2026-40972 affects spring boot. Severity is high (CVSS 7.5). 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 uploadin

How urgent is CVE-2026-40972?

Priority 31/100. High severity

Software pages

Spring Framework vulnerabilities · VMware vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.