CVE-2026-41001 Predictable Temp Directory in Artemis Auto-configuration
A local attacker can exploit a predictable temporary directory path in Spring Boot's embedded Artemis broker to perform symlink attacks, potentially leading to privilege escalation or data modification.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-41001?
CVE-2026-41001 is a medium-severity path traversal vulnerability in Spring Boot, published on 11 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Spring Boot's ArtemisEmbeddedConfigurationFactory uses a fixed, static path for the embedded Artemis message broker's data directory when no explicit path is configured. A local attacker on the same host can pre-create this predictable directory or place a symlink before the application starts.
Affected versions: 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.
Weakness: CWE-377
Which versions are affected by CVE-2026-41001?
10 open source packages ship an affected version, including org.springframework.boot:spring-boot-autoconfigure. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.springframework.boot:spring-boot-autoconfigure Maven | From 2.7.0 to 2.7.33 | None |
org.springframework.boot:spring-boot-autoconfigure Maven | From 2.7.0 to 2.7.33 | None |
org.springframework.boot:spring-boot-autoconfigure Maven | From 3.3.0 to 3.3.19 | None |
org.springframework.boot:spring-boot-autoconfigure Maven | From 3.3.0 to 3.3.19 | None |
org.springframework.boot:spring-boot-autoconfigure Maven | From 3.4.0 to 3.4.16 | None |
org.springframework.boot:spring-boot-autoconfigure Maven | From 3.4.0 to 3.4.16 | None |
4 more packages
org.springframework.boot:spring-boot-autoconfigure Maven | From 3.5.0 | 3.5.15 |
org.springframework.boot:spring-boot-autoconfigure Maven | From 3.5.0 | 3.5.15 |
org.springframework.boot:spring-boot-autoconfigure Maven | From 4.0.0 | 4.0.7 |
org.springframework.boot:spring-boot-autoconfigure Maven | From 4.0.0 | 4.0.7 |
Products include Vmware Spring Boot.
How do I fix CVE-2026-41001?
Upgrade org.springframework.boot:spring-boot-autoconfigure to a fixed version for your release line: 3.5.15 or 4.0.7.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-41001 being exploited?
There is no known exploitation of CVE-2026-41001 in the wild and no public exploit code.
Other vulnerabilities in Spring Boot
- CVE-2023-20873 Spring Boot Security Bypass with Wildcard Pattern Matching on Cloud Foundry
- CVE-2026-40976 Spring Boot's default security filter chain has no authorization rule with Actuator but without Health
- CVE-2026-22731 Authentication Bypass under Actuator Health groups paths
- CVE-2026-22733 Authentication Bypass under Actuator CloudFoundry endpoints
- CVE-2022-27772 Temporary Directory Hijacking to Local Privilege Escalation Vulnerability in org.springframework.boot:spring-boot
Sources
Also known as CLEANSTART-2026-LH44323, CLSA-2026-1781484842, CLSA-2026-1783645406, CLSA-2026-1785291688, CLSA-2026-1787668073, CLSA-2026-1787671361 and 11 more.