Classpath Path Traversal in Apache ActiveMQ
CVE-2026-33227 is an improper validation and restriction of a pathname vulnerability affecting multiple Apache ActiveMQ components, including ActiveMQ Client, Broker, All, Web, and ActiveMQ. In two code paths—when creating a STOMP consumer and when browsing messages in the web console—an authenticated user-controlled "key" value is concatenated into a path without sufficient validation, allowing traversal within the classpath. This can cause unintended classpath resource loading. Apache notes that the issue may be chainable with another attack to achieve further exploitation. Affected versions are ActiveMQ 5.x before 5.19.3 and 6.x from 6.0.0 before 6.2.2, with later clarification that the complete fix for Windows requires newer releases.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
2 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.
The version that knows your environment.
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.