CVE-2026-41001 is a medium-severity (CVSS 5.3) CWE-377 vulnerability in org.springframework.boot:spring-boot-autoconfigure. A fix is available for org.springframework.boot:spring-boot-autoconfigure — see the affected versions and patch details below.
Predictable Temp Directory in Artemis Auto-configuration
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41001.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-41001 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 383,485 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.springframework.boot:spring-boot-autoconfigure☕org.springframework.boot:spring-boot-autoconfigure☕org.springframework.boot:spring-boot-autoconfigure☕org.springframework.boot:spring-boot-autoconfigure☕org.springframework.boot:spring-boot-autoconfigureReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.boot:spring-boot-autoconfigure | ≥ 4.0.0&&< 4.0.7 | 4.0.7org.springframework.boot:spring-boot-autoconfigure:4.0.7 |
| ☕Maven | org.springframework.boot:spring-boot-autoconfigure | ≥ 3.5.0&&< 3.5.15 | 3.5.15org.springframework.boot:spring-boot-autoconfigure:3.5.15 |
| ☕Maven | org.springframework.boot:spring-boot-autoconfigure | ≥ 3.4.0 | No fix |
| ☕Maven | org.springframework.boot:spring-boot-autoconfigure | ≥ 3.3.0 | No fix |
| ☕Maven | org.springframework.boot:spring-boot-autoconfigure | ≥ 2.7.0 | No fix |
Affected Products
spring bootvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.boot:spring-boot-autoconfigure, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.boot:spring-boot-autoconfigure to 4.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41001 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
A flaw was found in Spring Boot. The embedded ActiveMQ Artemis broker uses a fixed, predictable path as the default data directory. A local attacker with access to the host can pre-create this directory to hijack message queue data, inject malicious messages, or potentially execute code via deserialization.…
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2026-41001 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-41001 in your dependencies?
Find it across Maven, including transitive dependencies.