CVE-2026-34197
Description
Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ.
Apache ActiveMQ Classic exposes the Jolokia JMX-HTTP bridge at /api/jolokia/ on the web console. The default Jolokia access policy permits exec operations on all ActiveMQ MBeans (org.apache.activemq:*), including
BrokerService.addNetworkConnector(String) and BrokerService.addConnector(String).
An authenticated attacker can invoke these operations with a crafted discovery URI that triggers the VM transport's brokerConfig parameter to load a remote Spring XML application context using ResourceXmlApplicationContext.
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 Broker: before 5.19.4, from 6.0.0 before 6.2.3; Apache ActiveMQ All: before 5.19.4, from 6.0.0 before 6.2.3; Apache ActiveMQ: before 5.19.4, from 6.0.0 before 6.2.3.
Users are recommended to upgrade to version 5.19.4 or 6.2.3, which fixes the issue
Summary dbcve.org
This vulnerability allows authenticated attackers to achieve remote code execution via the Jolokia JMX-HTTP bridge (/api/jolokia/) by invoking BrokerService.addNetworkConnector or BrokerService.addConnector with a crafted discovery URI. This triggers the VM transport's brokerConfig parameter to load a remote Spring XML application context via ResourceXmlApplicationContext, which instantiates singleton beans (including Runtime.exec() calls) before the BrokerService validates the configuration.
Mitigation
Upgrade to version 5.19.4 or 6.2.3; alternatively, disable or restrict the Jolokia endpoint and prevent network bridge/connector creation through authentication controls.