Vmware Spring Boot up to 4.0.5 temp file

Summaryinfo

A vulnerability was found in Vmware Spring Boot up to 2.7.32/3.3.18/3.4.15/3.5.13/4.0.5 and classified as critical. Affected by this issue is some unknown functionality. Such manipulation leads to temp file. This vulnerability is listed as CVE-2026-40973. The attack must be carried out locally. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Vmware Spring Boot up to 2.7.32/3.3.18/3.4.15/3.5.13/4.0.5 and classified as critical. Affected by this issue is an unknown code. The manipulation with an unknown input leads to a temp file vulnerability. Using CWE to declare the problem leads to CWE-377. Creating and using insecure temporary files can leave application and system data vulnerable to attack. Impacted is confidentiality, integrity, and availability. CVE summarizes:

A local attacker on the same host as the application may be able to take control of the directory used by `ApplicationTemp`. When `server.servlet.session.persistent` is set to `true` and the attack persists across application restarts, this may allow the attacker to read session information and hijack authenticated users or deploy a gadget chain and execute code as the application's user. 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); predictable temp directory / `ApplicationTemp` ownership verification. Versions that are no longer supported are also affected per vendor advisory.

The advisory is shared for download at spring.io. This vulnerability is handled as CVE-2026-40973 since 04/16/2026. The exploitation is known to be difficult. The attack needs to be approached locally. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 06/03/2026).

Upgrading to version 2.7.33, 3.3.19, 3.4.16, 3.5.14 or 4.0.6 eliminates this vulnerability.

The vulnerability is also documented in the databases at CNNVD (CNNVD-202604-5562) and CERT Bund (WID-SEC-2026-1263). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Affected

• Red Hat Enterprise Linux
• VMware Tanzu Spring Boot
• HCL Commerce
• Red Hat OpenShift

Productinfo

Vendor

• Vmware

Name

• Spring Boot

Version

• 2.7.0
• 2.7.1
• 2.7.2
• 2.7.3
• 2.7.4
• 2.7.5
• 2.7.6
• 2.7.7
• 2.7.8
• 2.7.9
• 2.7.10
• 2.7.11
• 2.7.12
• 2.7.13
• 2.7.14
• 2.7.15
• 2.7.16
• 2.7.17
• 2.7.18
• 2.7.19
• 2.7.20
• 2.7.21
• 2.7.22
• 2.7.23
• 2.7.24
• 2.7.25
• 2.7.26
• 2.7.27
• 2.7.28
• 2.7.29
• 2.7.30
• 2.7.31
• 2.7.32
• 3.3.0
• 3.3.1
• 3.3.2
• 3.3.3
• 3.3.4
• 3.3.5
• 3.3.6
• 3.3.7
• 3.3.8
• 3.3.9
• 3.3.10
• 3.3.11
• 3.3.12
• 3.3.13
• 3.3.14
• 3.3.15
• 3.3.16
• 3.3.17
• 3.3.18
• 3.4.0
• 3.4.1
• 3.4.2
• 3.4.3
• 3.4.4
• 3.4.5
• 3.4.6
• 3.4.7
• 3.4.8
• 3.4.9
• 3.4.10
• 3.4.11
• 3.4.12
• 3.4.13
• 3.4.14
• 3.4.15
• 3.5.0
• 3.5.1
• 3.5.2
• 3.5.3
• 3.5.4
• 3.5.5
• 3.5.6
• 3.5.7
• 3.5.8
• 3.5.9
• 3.5.10
• 3.5.11
• 3.5.12
• 3.5.13
• 4.0.0
• 4.0.1
• 4.0.2
• 4.0.3
• 4.0.4
• 4.0.5

License

• commercial

Website

• Vendor: https://www.vmware.com/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion