Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-wwpq-f5c3-7hvx

Spring Boot accepts predictable temp directory without ownership verification

CVSS 7.0 HighEPSS 0.0014 · 3rd percentile

Published by the GitHub Advisory Database at 28 Apr 2026, 00:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.springframework.boot:spring-bootMaven>=4.0.0, <4.0.6 || >=3.5.0, <3.5.14 || >=3.4.0, <=3.4.15 || >=3.3.0, <=3.3.18 || <=2.7.324.0.6, 3.5.14
Identifiers
GHSA-wwpq-f5c3-7hvx · CVE-2026-40973
Weakness (CWE)
CWE-377
Tags
Published
28 Apr 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Spring Boot (org.springframework.boot:spring-boot) versions 4.0.0 to before 4.0.6, 3.5.0 to before 3.5.14, 3.4.0 through 3.4.15, 3.3.0 through 3.3.18, and 2.7.32 and earlier are affected. A local attacker on the same host may be able to take control of the temporary directory used by ApplicationTemp, which can lead to session hijacking or code execution as the application user when persistent sessions are enabled. Upgrade to 4.0.6 or 3.5.14, or the fixed versions listed for the other branches.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.0 High 3.1 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H CNA (vmware)
  • CISA KEV Not listed.
  • EPSS 0.0014, the 3rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.