Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-ggg2-9786-hwc8

Spring Boot: Predictable Temp Directory in Artemis Auto-configuration

CVSS 5.3 MediumEPSS 0.0009 · 1st percentile

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

PackageEcosystemAffectedFixed in
org.springframework.boot:spring-boot-autoconfigureMaven>=4.0.0, <4.0.7 || >=3.5.0, <3.5.15 || >=3.4.0, <=3.4.16 || >=3.3.0, <=3.3.19 || >=2.7.0, <=2.7.334.0.7, 3.5.15
Identifiers
GHSA-ggg2-9786-hwc8 · CVE-2026-41001
Weakness (CWE)
CWE-377
Tags
Published
11 Jun 2026
Updated
10 Sept 2026

Machine-written summary

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

Spring Boot (spring-boot-autoconfigure) versions 4.0.0 to before 4.0.7, 3.5.0 to before 3.5.15, and earlier 2.7.x through 3.4.x releases are affected. When no data directory is configured for the embedded Artemis message broker, Spring Boot uses a fixed, predictable path. A local attacker on the same host who pre-creates that directory or places a symlink there before the application starts can interfere with the broker's data. Upgrade to 4.0.7 or 3.5.15, or set an explicit Artemis data directory path.

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
5.3 Medium 3.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L CNA (vmware)
  • CISA KEV Not listed.
  • EPSS 0.0009, the 1st 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.