CVE-2026-41001: Predictable Temp Directory in Artemis Auto-configuration

Published Jun 11, 2026
·
Updated

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 Software

6 affected components
maven/org.springframework.boot/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
VMware Spring Boot<2.7.34
VMware Spring Boot>=3.3.0<3.3.20
VMware Spring Boot>=3.4.0<3.4.17
VMware Spring Boot>=3.5.0<3.5.14.1
VMware Spring Boot>=4.0.0<4.0.6.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Spring Boot ArtemisEmbeddedConfigurationFactory / embedded Artemis message broker predictable temp directory to a version that resolves this vulnerability.

    Fixed in 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
  2. Configuration

    Configure Spring Boot to use an explicit embedded Artemis message broker data directory path (so ArtemisEmbeddedConfigurationFactory does not use the fixed static path for the embedded broker’s data directory).

    Spring Boot (ArtemisEmbeddedConfigurationFactory) / embedded Artemis message broker embedded Artemis message broker data directory path (explicit path vs default static fixed path) = Set an explicit data directory path instead of relying on the fixed, static default when no explicit path is configured

Event History

Jun 11, 2026
CVE Published
via MITRE·05:04 AM
Data Sourced
via MITRE·05:04 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 AM
DescriptionSeverityWeaknessAffected Software
Sep 1, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-41001?

The severity of CVE-2026-41001 is medium with a score of 5.3.

2

How do I fix CVE-2026-41001?

To fix CVE-2026-41001, ensure you configure a unique, explicit path for the Artemis message broker's data directory.

3

Who is affected by CVE-2026-41001?

CVE-2026-41001 affects applications using Spring Boot with the ArtemisEmbeddedConfigurationFactory without an explicitly configured data directory path.

4

What type of attack is possible due to CVE-2026-41001?

A local attacker can exploit CVE-2026-41001 by creating a predictable directory or placing a symlink to manipulate the embedded Artemis message broker's data.

5

When was CVE-2026-41001 published?

CVE-2026-41001 was published on June 11, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203