Loading vulnerability…
CVE-2026-41001 is an improper temporary-file-handling vulnerability in Spring Boot Artemis auto-configuration. ArtemisEmbeddedConfigurationFactory selects a fixed, static data-directory path for an embedded Apache ActiveMQ Artemis broker when no explicit broker data path is configured. A local attacker can prepare the predictable location, including by pre-creating it or replacing it with a symbolic link, before the affected application starts. Affected Spring Boot versions are 2.7.0 through 2.7.33, 3.3.0 through 3.3.19, 3.4.0 through 3.4.16, 3.5.0 through 3.5.14, and 4.0.0 through 4.0.6.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity local predictable temporary-directory/symlink vulnerability in Spring Boot's ArtemisEmbeddedConfigurationFactory. A local authenticated attacker may pre-create or symlink the static embedded Artemis broker data directory before application startup, potentially affecting confidentiality, integrity, and availability.
A local vulnerability in Spring Boot's Artemis auto-configuration caused by use of a predictable static data directory for the embedded Artemis broker, enabling directory hijacking, message injection, data compromise, and potential code execution via deserialization attacks through the journal.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.