Evidence used
- No CISA KEV confirmation is currently recorded.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 0.13% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-41001High confidence
Predictable Temp Directory in Artemis Auto-configuration
Spring · Spring Boot
5.3MediumCVSS 3.1
Scheduled
Fix not verifiedMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Low, lowered one band.downgradedsince 23 Jun 2026
Compensating controls
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Spring Spring Boot and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Open-source package ranges10 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Mavenorg.springframework.boot:spring-boot-autoconfigure | ECOSYSTEM: introduced 4.0.0; fixed 4.0.7 | 4.0.7 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.springframework.boot:spring-boot-autoconfigure | ECOSYSTEM: introduced 3.5.0; fixed 3.5.15 | 3.5.15 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.springframework.boot:spring-boot-autoconfigure | ECOSYSTEM: introduced 3.4.0; last affected 3.4.16 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.springframework.boot:spring-boot-autoconfigure | ECOSYSTEM: introduced 3.3.0; last affected 3.3.19 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.springframework.boot:spring-boot-autoconfigure | ECOSYSTEM: introduced 2.7.0; last affected 2.7.33 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| mavenorg.springframework.boot:spring-boot-autoconfigure | >= 4.0.0, <= 4.0.6 | 4.0.7 | GitHub advisory ↗github reviewed aggregator · 21 Aug 2026 |
| mavenorg.springframework.boot:spring-boot-autoconfigure | >= 3.5.0, <= 3.5.14 | 3.5.15 | GitHub advisory ↗github reviewed aggregator · 21 Aug 2026 |
| mavenorg.springframework.boot:spring-boot-autoconfigure | >= 3.4.0, <= 3.4.16 | Not stated | GitHub advisory ↗github reviewed aggregator · 21 Aug 2026 |
| mavenorg.springframework.boot:spring-boot-autoconfigure | >= 3.3.0, <= 3.3.19 | Not stated | GitHub advisory ↗github reviewed aggregator · 21 Aug 2026 |
| mavenorg.springframework.boot:spring-boot-autoconfigure | >= 2.7.0, <= 2.7.33 | Not stated | GitHub advisory ↗github reviewed aggregator · 21 Aug 2026 |
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Fix not verified01
What, why and how
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.
What
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.
Why
Creating and using insecure temporary files can leave application and system data vulnerable to attack.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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.
Why
Creating and using insecure temporary files can leave application and system data vulnerable to attack.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Insecure Temporary File → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-377 ↗
CWE-377: Insecure Temporary File. Creating and using insecure temporary files can leave application and system data vulnerable to attack.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:LCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ALowAvailability impact: A successful attack can cause a limited loss.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix not verified
- Affected
- Spring Boot: 4.0.0 < 4.0.6.1, 3.5.0 < 3.5.14.1, 3.4.0 < 3.4.17, 3.3.0 < 3.3.20, 2.7.0 < 2.7.34
- Fixed
- No fixed version is explicitly recorded in the structured CVE data.
- Action
- No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 11 Jun 2026 · Last source change 23 Jun 2026, 19:54 UTC · CWE-377 · Insecure Temporary File
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-36211
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: spring.io/cve-2026-41001.security@vmware.com ↗
- Before
- no authoritative guidance recorded
- After
- vendor advisory: spring.io/cve-2026-41001
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.