Loading vulnerability…
CVE-2026-41044 is an authenticated remote code execution vulnerability in Apache ActiveMQ, Apache ActiveMQ Broker, and Apache ActiveMQ All. The flaw stems from improper input validation of broker names combined with code injection behavior in the broker configuration loading path. An authenticated attacker can use the administrative web console to create a malicious broker name that bypasses validation and embeds an xbean binding. That broker name can later be referenced through VM transport creation triggered via the DestinationView MBean exposed by Jolokia, causing the broker to load a remote Spring XML application context. Because Spring's ResourceXmlApplicationContext instantiates singleton beans before BrokerService completes configuration validation, attacker-controlled bean definitions can be executed during context initialization, resulting in arbitrary code execution on the broker JVM, including through bean factory methods such as Runtime.exec(). The issue affects Apache ActiveMQ, Apache ActiveMQ Broker, and Apache ActiveMQ All before 5.19.6, and versions 6.0.0 through before 6.2.5.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
9 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.