CVE-2026-40973: CWE-377: Insecure Temporary File in Spring Spring Boot
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.
AI Analysis
Technical Summary
This vulnerability (CVE-2026-40973) affects multiple Spring Boot versions from 2.7.0 to 4.0.5. It involves insecure temporary file handling (CWE-377) where the ApplicationTemp directory can be controlled by a local attacker on the same host. If server.servlet.session.persistent is enabled, the attacker can persist the attack across application restarts, potentially reading session information, hijacking authenticated sessions, or deploying gadget chains to execute arbitrary code as the application user. The issue is due to predictable temporary directory usage and insufficient ownership verification. Official fixes are available in Spring Boot versions 4.0.6, 3.5.14, 3.4.16, 3.3.19, and 2.7.33.
Potential Impact
An attacker with local access to the host can exploit this vulnerability to read sensitive session information, hijack authenticated user sessions, and execute arbitrary code with the application's privileges. This can lead to full compromise of the application environment. The CVSS score of 7.0 reflects high impact on confidentiality, integrity, and availability. No known exploits in the wild have been reported yet.
Mitigation Recommendations
Official fixes are available in Spring Boot versions 4.0.6, 3.5.14, 3.4.16, 3.3.19, and 2.7.33. Users should upgrade to these or later versions to remediate the vulnerability. Since this is not a cloud service, patching the affected Spring Boot application versions is required. Patch status is confirmed by the vendor advisory. No additional mitigation steps are indicated beyond applying the official fixes.
CVE-2026-40973: CWE-377: Insecure Temporary File in Spring Spring Boot
Description
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.
CVSS v3.1
Score 7.0high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CVE-2026-40973) affects multiple Spring Boot versions from 2.7.0 to 4.0.5. It involves insecure temporary file handling (CWE-377) where the ApplicationTemp directory can be controlled by a local attacker on the same host. If server.servlet.session.persistent is enabled, the attacker can persist the attack across application restarts, potentially reading session information, hijacking authenticated sessions, or deploying gadget chains to execute arbitrary code as the application user. The issue is due to predictable temporary directory usage and insufficient ownership verification. Official fixes are available in Spring Boot versions 4.0.6, 3.5.14, 3.4.16, 3.3.19, and 2.7.33.
Potential Impact
An attacker with local access to the host can exploit this vulnerability to read sensitive session information, hijack authenticated user sessions, and execute arbitrary code with the application's privileges. This can lead to full compromise of the application environment. The CVSS score of 7.0 reflects high impact on confidentiality, integrity, and availability. No known exploits in the wild have been reported yet.
Mitigation Recommendations
Official fixes are available in Spring Boot versions 4.0.6, 3.5.14, 3.4.16, 3.3.19, and 2.7.33. Users should upgrade to these or later versions to remediate the vulnerability. Since this is not a cloud service, patching the affected Spring Boot application versions is required. Patch status is confirmed by the vendor advisory. No additional mitigation steps are indicated beyond applying the official fixes.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- vmware
- Date Reserved
- 2026-04-16T02:18:56.133Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69f0134ecbff5d861057a5c8
Added to database: 4/28/2026, 1:54:22 AM
Last enriched: 5/5/2026, 2:42:49 AM
Last updated: 6/12/2026, 9:41:00 AM
Views: 151
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.