Is CVE-2026-40973 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-40973 being exploited in the wild.

How severe is CVE-2026-40973?

High severity, with a CVSS score of 7, published 28 April 2026.

Which products and versions are affected?

org.springframework.boot:spring-boot (Maven) ECOSYSTEM:introduced=4.0.0,fixed=4.0.6; VMware Spring Boot 4.0.0–4.0.5, 3.5.0–3.5.13, 3.4.0–3.4.15, 3.3.0–3.3.18, 2.7.0–2.7.32.

Is there a fix for CVE-2026-40973?

Yes. org.springframework.boot:spring-boot (Maven): upgrade to 4.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-40973 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-40973?

Check whether you run org.springframework.boot:spring-boot (Maven) or VMware Spring Boot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-40973: VMware Spring Boot insecure temporary directory in ApplicationTemp

CVE-2026-40973 · Severity: high · CVSS 7 · Published 2026-04-28

Spring Boot is a popular framework used to build and run Java-based web applications. A security flaw allows a local attacker with access to the same server to take control of the application's temporary directory. This could lead to the theft of user session data, account hijacking, or the ability to execute malicious code as the application user.

Technologies: org.springframework.boot:spring-boot (Maven), VMware Spring Boot. Vendors: Maven, VMware.

Quick answers

Is CVE-2026-40973 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-40973 being exploited in the wild.
How severe is CVE-2026-40973?: High severity, with a CVSS score of 7, published 28 April 2026.
Which products and versions are affected?: org.springframework.boot:spring-boot (Maven) ECOSYSTEM:introduced=4.0.0,fixed=4.0.6; VMware Spring Boot 4.0.0–4.0.5, 3.5.0–3.5.13, 3.4.0–3.4.15, 3.3.0–3.3.18, 2.7.0–2.7.32.
Is there a fix for CVE-2026-40973?: Yes. org.springframework.boot:spring-boot (Maven): upgrade to 4.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-40973 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-40973?: Check whether you run org.springframework.boot:spring-boot (Maven) or VMware Spring Boot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.springframework.boot:spring-boot (Maven): upgrade to 4.0.6 or later

# set org.springframework.boot:spring-boot to 4.0.6 in your pom.xml or build.gradle

Technical details

An insecure temporary file vulnerability (CWE-377) exists in Spring Boot's ApplicationTemp component due to predictable directory naming and insufficient ownership verification. A local attacker with low privileges can pre-create or take control of this directory. If the application is configured with persistent sessions (server.servlet.session.persistent=true), the attacker can read session data across restarts or deploy a gadget chain to achieve arbitrary code execution in the context of the application user. The vulnerability is mitigated by upgrading to versions 4.0.6, 3.5.14, 3.4.16, 3.3.19, or 2.7.33.

Affected products

VMware Spring Boot 4.0.0–4.0.5, 3.5.0–3.5.13, 3.4.0–3.4.15, 3.3.0–3.3.18, 2.7.0–2.7.32

Identifiers

CVE-2026-40973
GHSA-wwpq-f5c3-7hvx

Timeline

2026-04-27: advisory: Initial advisory published by VMware
2026-04-28: disclosed: NVD publication date

References

https://spring.io/security/cve-2026-40973

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.