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 (CWE-377) arises from predictable temporary directory usage and insufficient ownership verification in Spring Boot's ApplicationTemp component when persistent sessions are enabled. A local attacker with low privileges on the host can potentially manipulate the directory across application restarts to access sensitive session information or deploy malicious gadget chains for code execution under the application's user context. The issue affects multiple Spring Boot versions from 2.7.0 to 4.0.5 and has been addressed in subsequent patch releases.
Potential Impact
Successful exploitation allows a local attacker to read session information, hijack authenticated user sessions, and execute arbitrary code as the application user. This compromises confidentiality, integrity, and availability of the affected application environment.
Mitigation Recommendations
Fixed versions are available: upgrade to Spring Boot 2.7.33, 3.3.19, 3.4.16, 3.5.14, or 4.0.6 or later. Since no official patch links or vendor advisory text were provided, verify patch availability and apply updates accordingly. Until patched, avoid enabling server.servlet.session.persistent or restrict local access to the host to trusted users only.
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CWE-377) arises from predictable temporary directory usage and insufficient ownership verification in Spring Boot's ApplicationTemp component when persistent sessions are enabled. A local attacker with low privileges on the host can potentially manipulate the directory across application restarts to access sensitive session information or deploy malicious gadget chains for code execution under the application's user context. The issue affects multiple Spring Boot versions from 2.7.0 to 4.0.5 and has been addressed in subsequent patch releases.
Potential Impact
Successful exploitation allows a local attacker to read session information, hijack authenticated user sessions, and execute arbitrary code as the application user. This compromises confidentiality, integrity, and availability of the affected application environment.
Mitigation Recommendations
Fixed versions are available: upgrade to Spring Boot 2.7.33, 3.3.19, 3.4.16, 3.5.14, or 4.0.6 or later. Since no official patch links or vendor advisory text were provided, verify patch availability and apply updates accordingly. Until patched, avoid enabling server.servlet.session.persistent or restrict local access to the host to trusted users only.
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: 4/28/2026, 1:54:37 AM
Last updated: 4/28/2026, 3:36:57 AM
Views: 2
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.