# 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. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`) - **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:** Yes - **Published:** 11 Jun 2026 - **Updated:** 23 Jun 2026 - **Also known as:** CLEANSTART-2026-LH44323, CLSA-2026-1781484842, CLSA-2026-1783645406, CLSA-2026-1785291688, CLSA-2026-1787668073, CLSA-2026-1787671361, CLSA-2026-1787673713, ECHO-4915-a49a-697b, GHSA-ggg2-9786-hwc8, MINI-4xjv-x3q8-648c, MINI-7vc5-8j3h-2c65, MINI-gh6f-m4g7-8vww, MINI-gp83-cxrw-wc6v, MINI-h79c-97fm-46rv, MINI-pmxh-v342-8c4q, RHLW-2026-0a4e3ce968cb9794, ROOT-APP-MAVEN-CVE-2026-41001 ## 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 (DEPRECATED: Insecure Temporary File) ## 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 | Ecosystem | 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 | | `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: 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. ## 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](https://insights.sbomify.com/CVE-2023-20873/): Spring Boot Security Bypass with Wildcard Pattern Matching on Cloud Foundry (critical 9.8) - [CVE-2026-40976](https://insights.sbomify.com/CVE-2026-40976/): Spring Boot's default security filter chain has no authorization rule with Actuator but without Health (critical 9.1) - [CVE-2026-22731](https://insights.sbomify.com/CVE-2026-22731/): Authentication Bypass under Actuator Health groups paths (high 8.2) - [CVE-2026-22733](https://insights.sbomify.com/CVE-2026-22733/): Authentication Bypass under Actuator CloudFoundry endpoints (high 8.2) - [CVE-2022-27772](https://insights.sbomify.com/CVE-2022-27772/): Temporary Directory Hijacking to Local Privilege Escalation Vulnerability in org.springframework.boot:spring-boot (high 7.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-41001 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2026-41001 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework.boot:spring-boot-autoconfigure (Maven): affected from 2.7.0 up to 2.7.33; no fix listed - org.springframework.boot:spring-boot-autoconfigure (Maven): affected from 2.7.0 up to 2.7.33; no fix listed - org.springframework.boot:spring-boot-autoconfigure (Maven): affected from 3.3.0 up to 3.3.19; no fix listed - org.springframework.boot:spring-boot-autoconfigure (Maven): affected from 3.3.0 up to 3.3.19; no fix listed - org.springframework.boot:spring-boot-autoconfigure (Maven): affected from 3.4.0 up to 3.4.16; no fix listed - org.springframework.boot:spring-boot-autoconfigure (Maven): affected from 3.4.0 up to 3.4.16; no fix listed - org.springframework.boot:spring-boot-autoconfigure (Maven): affected from 3.5.0; fixed in 3.5.15 - org.springframework.boot:spring-boot-autoconfigure (Maven): affected from 3.5.0; fixed in 3.5.15 - org.springframework.boot:spring-boot-autoconfigure (Maven): affected from 4.0.0; fixed in 4.0.7 - org.springframework.boot:spring-boot-autoconfigure (Maven): affected from 4.0.0; fixed in 4.0.7 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-41001/ (Markdown: https://insights.sbomify.com/CVE-2026-41001/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41001 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41001 - OSV: https://osv.dev/vulnerability/CVE-2026-41001 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-41001/ Summaries are generated and may contain mistakes; the official description above is the record.