CVSS 3.1
5.3 mediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:LMedium (5.3) in vmware spring boot. EPSS 0.09% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.boot:spring-boot-autoconfigure 3.5.15, 4.0.7.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:Lorg.springframework.boot:spring-boot-autoconfigure (Maven): fixed in 4.0.7, 3.5.15Explain CVE-2026-41001 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-41001?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-41001?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-41001 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Spring Boot | from 4.0.0 before 4.0.6.1 |
| Spring Boot | from 3.5.0 before 3.5.14.1 |
| Spring Boot | from 3.4.0 before 3.4.17 |
| Spring Boot | from 3.3.0 before 3.3.20 |
| Spring Boot | from 2.7.0 before 2.7.34 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-ggg2-9786-hwc8 | Maven | org.springframework.boot:spring-boot-autoconfigure | >=4.0.0 <4.0.7 | 4.0.7 |
| GHSA-ggg2-9786-hwc8 | Maven | org.springframework.boot:spring-boot-autoconfigure | >=3.5.0 <3.5.15 | 3.5.15 |
| GHSA-ggg2-9786-hwc8 | Maven | org.springframework.boot:spring-boot-autoconfigure | >=3.4.0 <=3.4.16 | no fix published |
| GHSA-ggg2-9786-hwc8 | Maven | org.springframework.boot:spring-boot-autoconfigure | >=3.3.0 <=3.3.19 | no fix published |
| GHSA-ggg2-9786-hwc8 | Maven | org.springframework.boot:spring-boot-autoconfigure | >=2.7.0 <=2.7.33 | no fix published |
Red Hat rates this Moderate.
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. Exploitation requires local access, use of the embedded Artemis broker (not external), and no custom data directory configured. Red Hat products using external message brokers or not using Artemis at all are not affected.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat AMQ Clients | spring-boot | Fix deferred | |
| Red Hat build of Apache Camel - HawtIO 4 | spring-boot | Fix deferred | |
| Red Hat Data Grid 8 | spring-boot | Fix deferred | |
| Red Hat Enterprise Linux 8 | log4j:2/log4j | Fix deferred | |
| Red Hat JBoss Enterprise Application Platform Expansion Pack | spring-boot | Fix deferred | |
| Red Hat OpenShift Dev Spaces | devspaces/openvsx-rhel9 | Not affected | |
| Red Hat OpenShift Dev Spaces | devspaces/pluginregistry-rhel9 | Not affected | |
| Red Hat Single Sign-On 7 | spring-boot | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-41001.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.