Sovra Recon·Actively exploited

CVE-2026-34197Apache ActiveMQ Improper Input Validation Vulnerability

At a glance

CVE-2026-34197 is a high-severity vulnerability (CVSS score 8.8) affecting ActiveMQ (Apache). CISA has confirmed that attackers have been exploiting it since April 16, 2026.

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

Details

The vulnerability in detail

CVE ID
CVE-2026-34197
Vendor
Apache
Product
ActiveMQ
Severity (CVSS)
High · 8.8 / 10
Published
April 7, 2026
Actively exploited
Yes, confirmed by CISA on April 16, 2026
Used in ransomware
Not reported
CERT-FR advisory (in French)
CERTFR-2026-AVI-1206
Weakness type (CWE)
CWE-20, CWE-94

What to do

How to protect against CVE-2026-34197

  • Check whether you are affected: apachectl -v (or httpd -v) for the web server, version.sh in the Tomcat folder; for a library such as Log4j, look up its version in the application's dependencies.
  • Apply the vendor's patch as a priority on Internet-facing systems, since this vulnerability is already being exploited.
  • If no patch is available, apply the published workarounds or take the service off the Internet.
  • Look for signs of compromise: a vulnerability exploited before you patched may already have been used. Review your logs and the indicators published by the vendor.

Sources

Official descriptions from NVD and CISA, in their original wording.

Patching a CVE is not enough.

The vulnerabilities specific to your application have no CVE. Our AI agents hunt for them by actually attacking your systems.