Executive brief
Apache ActiveMQ is a popular open-source message broker used to facilitate communication between different software applications. A security vulnerability in its management console allows an authenticated user to execute unauthorized commands on the server hosting the broker. This could lead to a complete system takeover, data theft, or disruption of business operations.
Technical details
A code injection vulnerability exists in Apache ActiveMQ Classic's Jolokia JMX-HTTP bridge (/api/jolokia/). The default Jolokia access policy allows authenticated attackers to execute operations on ActiveMQ MBeans, specifically BrokerService.addNetworkConnector and BrokerService.addConnector. By supplying a crafted discovery URI containing a 'brokerConfig' parameter, an attacker can force the application to load a remote Spring XML application context via ResourceXmlApplicationContext. Because Spring instantiates singleton beans before the BrokerService validates the configuration, an attacker can achieve arbitrary code execution on the JVM (e.g., via Runtime.exec()). This issue is fixed in versions 5.19.4 and 6.2.3.
Affected products
- Apache ActiveMQ Broker before 5.19.4, 6.0.0 before 6.2.3
- Apache ActiveMQ All before 5.19.4, 6.0.0 before 6.2.3
Timeline
- 2026-04-06: disclosed: Initial disclosure on oss-security mailing list
- 2026-04-07: advisory: NVD publication date
- 2026-04-16: kev added: Added to CISA Known Exploited Vulnerabilities catalog
References
- https://repo.maven.apache.org/maven2
- https://activemq.apache.org/security-advisories.data/CVE-2026-34197-announcement.txt
- http://www.openwall.com/lists/oss-security/2026/04/06/3
- https://access.redhat.com/security/cve/CVE-2026-34197
- https://bugzilla.redhat.com/show_bug.cgi?id=2455869
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-34197.json