CVE-2026-34197 Apache ActiveMQ Improper Input Validation
Authenticated attackers can achieve remote code execution on Apache ActiveMQ brokers by exploiting Jolokia MBeans to load malicious Spring XML configurations.
- Exploited in the wild
- Since 16 Apr 2026
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-34197?
CVE-2026-34197 is a high-severity code injection vulnerability in Apache Activemq, published on 7 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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
Which versions are affected by CVE-2026-34197?
9 open source packages ship an affected version, including org.apache.activemq:activemq-all, activemq and org.apache.activemq:activemq-broker. It affects 2 products.
| Package | Affected | Fixed in |
|---|---|---|
org.apache.activemq:activemq-all Maven | All versions | 5.19.5 |
org.apache.activemq:activemq-all Maven | All versions | 5.19.5 |
org.apache.activemq:activemq-all Maven | From 6.0.0 | 6.2.3 |
org.apache.activemq:activemq-all Maven | From 6.0.0 | 6.2.3 |
activemq Bitnami | All versions | 5.19.4, 6.2.3 |
org.apache.activemq:activemq-broker Maven | All versions | 5.19.5 |
3 more packages
org.apache.activemq:activemq-broker Maven | All versions | 5.19.5 |
org.apache.activemq:activemq-broker Maven | From 6.0.0 | 6.2.3 |
org.apache.activemq:activemq-broker Maven | From 6.0.0 | 6.2.3 |
Products include Apache Activemq, Apache Activemq Broker.
How do I fix CVE-2026-34197?
Upgrade org.apache.activemq:activemq-all to a fixed version for your release line: 5.19.5 or 6.2.3. US federal agencies must fix it by 30 Apr 2026.
Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.
Is CVE-2026-34197 being exploited?
Yes. Attackers have exploited CVE-2026-34197 in the wild since at least 16 Apr 2026.
Public exploit code: 1 Metasploit module, 1 Nuclei template and 14 proofs of concept on GitHub.
Other vulnerabilities in Apache Activemq
- CVE-2023-46604 Apache ActiveMQ Deserialization of Untrusted Data
- CVE-2016-3088 Apache ActiveMQ Improper Input Validation
- CVE-2020-11998 Remote code execution in Apache ActiveMQ
- CVE-2013-7285 Command Injection in Xstream
- CVE-2014-3600 Improper Restriction of XML External Entity Reference in Apache ActiveMQ
Sources
Also known as BIT-activemq-2026-34197, CLSA-2026-1790690736, DEBIAN-CVE-2026-34197, GHSA-rxpj-7qvf-xv32, MINI-45x5-qf32-c9vj, MINI-844g-gv3j-wwgm and 7 more.