CVE-2026-34197

published 7 Apr 2026 · updated 17 Aug 2026

Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Authenticated users could perform RCE via Jolokia MBeans

10.0CriticalCVSS 8.8EPSS 98%CISA KEV · due 30 Apr 20262 public exploits

Exploited in the wild, in CISA KEV since 16 Apr 2026 (due 30 Apr 2026), with 2 public exploits. Fixed in 6.2.3 and 5.19.4.

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

Briefing

Written from the sources below · deepseek-v4.1-flash

Apache ActiveMQ Classic's default Jolokia policy allows exec on all ActiveMQ MBeans, letting an authenticated attacker invoke broker connector operations with a crafted URI that loads a remote Spring XML context and executes code. Versions before 5.19.4 and 6.0.0 through 6.2.3 are affected.

Why it mattersListed in CISA KEV with confirmed exploitation, public nuclei templates and 98% EPSS, so exposed brokers are at high risk of active attack.

ActionUpgrade Apache ActiveMQ to 5.19.4 or 6.2.3, or restrict Jolokia exec access on org.apache.activemq MBeans.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
ApacheActiveMQ
Apache Software Foundation>=6.0.0 <6.2.3, <5.19.46.2.3, 5.19.4

Exploit evidence

2 public sources

kev

Timeline

Every event on this vulnerability

Public exploitCVE-2026-34197·
Apache ActiveMQ Classic's default Jolokia policy allows exec on all ActiveMQ MBeans, letting an authenticated attacker invoke broker connector operations with a crafted URI that loads a remote Spring XML context and executes code. Versions before 5.19.4 and 6.0.0 through 6.2.3 are affected.
10.0Critical

Related

Other vulnerabilities in ActiveMQ, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-34197 severity on Zeptric[![CVE-2026-34197](https://zeptric.io/badge/cve/CVE-2026-34197.svg)](https://zeptric.io/cve/CVE-2026-34197)