Actively exploited in the wild
Apache ActiveMQ Improper Input Validation Vulnerability
Apache — ActiveMQ · Listed in the CISA KEV since 2026-04-16. This indicates confirmed attacks in production environments.
Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CVE-2026-34197
HighCVSS 8.8KEVExploitation Probability (EPSS)
Very high risk100th percentile — higher than 100% of all known CVEs
Summary
A vulnerability in Apache ActiveMQ allows an authenticated attacker to achieve remote code execution via the Jolokia JMX-HTTP endpoint. It stems from improper input validation and code injection, enabling arbitrary code execution on the broker's JVM.
Risk Assessment
The risk for the organization includes full compromise of the ActiveMQ broker, potentially leading to data theft, service disruption, or further attacks on internal infrastructure.
Recommendation
Immediately upgrade Apache ActiveMQ to version 5.19.4 or 6.2.3, which fix this vulnerability. Additionally, restrict access to the Jolokia endpoint to trusted networks only.
Original NVD description (English source)
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