CVE-2026-41001: VMware Spring Boot insecure directory in ArtemisEmbeddedConfigurationFactory

CVE-2026-41001 · Severity: medium · CVSS 5.3 · Published 2026-06-11

Spring Boot applications using embedded Artemis message broker use a fixed, predictable directory path for storing broker data when no explicit path is configured. A local attacker with low privileges on the same system can exploit this by pre-creating the directory or placing a symlink before the application starts, allowing unauthorized access to or modification of sensitive message broker data.

Technologies: VMware Spring Boot. Vendors: Maven, VMware.

Quick answers

Is CVE-2026-41001 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-41001 being exploited in the wild.
How severe is CVE-2026-41001?
Medium severity, with a CVSS score of 5.3, published 11 June 2026.
Which products and versions are affected?
org.springframework.boot:spring-boot-autoconfigure (Maven) ECOSYSTEM:introduced=4.0.0,fixed=4.0.7; VMware Spring Boot 4.0.0 through 4.0.6; 3.5.0 through 3.5.14; 3.4.0 through 3.4.16; 3.3.0 through 3.3.19; 2.7.0 through 2.7.33, 4.0.0-4.0.6, 3.5.0-3.5.14, 3.4.0-3.4.16, 3.3.0-3.3.19, 2.7.0-2.7.33; VMware Spring-Boot-Autoconfigure 4.0.0-4.0.6, 3.5.0-3.5.14, 3.4.0-3.4.16, 3.3.0-3.3.19, 2.7.0-2.7.33.
Is there a fix for CVE-2026-41001?
Yes. org.springframework.boot:spring-boot-autoconfigure (Maven): upgrade to 4.0.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41001 attacked?
It is attacked with local access, in a software library.
Am I affected by CVE-2026-41001?
Check whether you run org.springframework.boot:spring-boot-autoconfigure (Maven), VMware Spring Boot or VMware Spring-Boot-Autoconfigure at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.springframework.boot:spring-boot-autoconfigure (Maven): upgrade to 4.0.7 or later
    # set org.springframework.boot:spring-boot-autoconfigure to 4.0.7 in your pom.xml or build.gradle

Technical details

The vulnerability is an insecure temporary file creation issue (CWE-377) in Spring Boot's ArtemisEmbeddedConfigurationFactory class. When auto-configuring an embedded Artemis message broker without an explicit data directory path, the factory uses a hardcoded, predictable directory location. A local attacker with low privileges can exploit this by creating a directory or symlink at the known path before the Spring Boot application starts. This allows the attacker to intercept or manipulate the Artemis data directory. The attack requires local access to the system and no user interaction. The fix involves updating ArtemisEmbeddedConfigurationFactory to use the secure ApplicationTemp class for generating the data directory path, ensuring the location is randomly generated rather than predictable. Patches are available for versions 4.0.7 and 3.5.15; older branches (3.4, 3.3, 2.7) do not have publicly available patches.

Affected products

  • Spring Spring Boot 4.0.0-4.0.6, 3.5.0-3.5.14, 3.4.0-3.4.16, 3.3.0-3.3.19, 2.7.0-2.7.33
  • Spring spring-boot-autoconfigure 4.0.0-4.0.6, 3.5.0-3.5.14, 3.4.0-3.4.16, 3.3.0-3.3.19, 2.7.0-2.7.33

Identifiers

  • CVE-2026-41001
  • GHSA-ggg2-9786-hwc8

Timeline

  • 2026-06-11: disclosed: Published to GitHub Advisory Database
  • 2026-06-11: patched: Spring Boot 4.0.7 and 3.5.15 released with fix

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.