High [CVE-2026-41044] Apache ActiveMQ, Apache ActiveMQ Broker, Apache ActiveMQ All: Authenticated user can perform RCE via DestinationView MBean exposed by Jolokia
This high-severity Apache Software Foundation advisory covers CVE-2026-41044 affecting Apache ActiveMQ Broker, Apache ActiveMQ All.
Android app · Google Play
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ, Apache ActiveMQ Broker, Apache ActiveMQ All.
An authenticated attacker can use the admin web console page to construct a malicious broker name that bypasses name validation to include an xbean binding that can be later used by a VM transport to load a remote Spring XML application.
The attacker can then use the DestinationView mbean to send a message to trigger a VM transport creation that will reference this malicious broker name which can lead to loading the malicious Spring XML context file.
Because Spring's ResourceXmlApplicationContext instantiates all singleton beans before the BrokerService validates the configuration, arbitrary code execution occurs on the broker's JVM through bean factory methods such as Runtime.exec().
This issue affects Apache ActiveMQ: before 5.19.6, from 6.0.0 before 6.2.5; Apache ActiveMQ Broker: before 5.19.6, from 6.0.0 before 6.2.5; Apache ActiveMQ All: before 5.19.6, from 6.0.0 before 6.2.5. Users are recommended to upgrade to version 6.2.5 or 5.19.6, which fixes the issue.
- Apache ActiveMQ before 5.19.6
- Apache ActiveMQ 6.0.0 before 6.2.5
- Apache ActiveMQ Broker before 5.19.6
- Apache ActiveMQ Broker 6.0.0 before 6.2.5
- Apache ActiveMQ All before 5.19.6
- Apache ActiveMQ All 6.0.0 before 6.2.5
Official advisory · high-confidence parse· fetched 1 month ago·verify at source
- 5.19.6
- 6.2.5
Official advisory · high-confidence parse· fetched 1 month ago·verify at source
Mitigation checklist
- Users are recommended to upgrade to version 6.2.5 or 5.19.6, which fixes the issue.
Official advisory · high-confidence parse· fetched 1 month ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.