CVE-2026-34197: Apache ActiveMQ code injection in Jolokia JMX-HTTP bridge

CVE-2026-34197 · Severity: critical · CVSS 8.8 · Exploited in the wild · Published 2026-04-07

Apache ActiveMQ is a popular open-source message broker used to facilitate communication between different software applications. A security vulnerability in its management console allows an authenticated user to execute unauthorized commands on the server hosting the broker. This could lead to a complete system takeover, data theft, or disruption of business operations.

Technologies: Apache ActiveMQ, Apache Activemq Broker, org.apache.activemq:activemq-all (Maven), org.apache.activemq:activemq-broker (Maven). Vendors: Apache, Maven.

Quick answers

Is CVE-2026-34197 exploited in the wild?
Yes. CVE-2026-34197 is known to be exploited in the wild, first recorded on 16 April 2026. Treat it as urgent.
How severe is CVE-2026-34197?
Critical severity, with a CVSS score of 8.8, published 7 April 2026.
Which products and versions are affected?
Apache ActiveMQ < 5.19.4, 6.0.0 to < 6.2.3, before 5.19.4, 6.0.0 before 6.2.3; Apache ActiveMQ Classic < 5.19.5, >= 6.0.0, < 6.2.3; Apache Activemq Broker < 5.19.4, 6.0.0 to < 6.2.3; org.apache.activemq:activemq-all (Maven) ECOSYSTEM:introduced=0,fixed=5.19.5; and 1 more.
Is there a fix for CVE-2026-34197?
Yes. org.apache.activemq:activemq-all (Maven): upgrade to 5.19.5 or later; org.apache.activemq:activemq-broker (Maven): upgrade to 5.19.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-34197 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-34197?
Check whether you run Apache ActiveMQ, Apache ActiveMQ Classic, Apache Activemq Broker or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.apache.activemq:activemq-all (Maven): upgrade to 5.19.5 or later
    # set org.apache.activemq:activemq-all to 5.19.5 in your pom.xml or build.gradle
  • org.apache.activemq:activemq-broker (Maven): upgrade to 5.19.5 or later
    # set org.apache.activemq:activemq-broker to 5.19.5 in your pom.xml or build.gradle

Technical details

A code injection vulnerability exists in Apache ActiveMQ Classic's Jolokia JMX-HTTP bridge (/api/jolokia/). The default Jolokia access policy allows authenticated attackers to execute operations on ActiveMQ MBeans, specifically BrokerService.addNetworkConnector and BrokerService.addConnector. By supplying a crafted discovery URI containing a 'brokerConfig' parameter, an attacker can force the application to load a remote Spring XML application context via ResourceXmlApplicationContext. Because Spring instantiates singleton beans before the BrokerService validates the configuration, an attacker can achieve arbitrary code execution on the JVM (e.g., via Runtime.exec()). This issue is fixed in versions 5.19.4 and 6.2.3.

Affected products

  • Apache ActiveMQ Broker before 5.19.4, 6.0.0 before 6.2.3
  • Apache ActiveMQ All before 5.19.4, 6.0.0 before 6.2.3

Identifiers

  • CVE-2026-34197
  • GHSA-rxpj-7qvf-xv32

Timeline

  • 2026-04-06: disclosed: Initial disclosure on oss-security mailing list
  • 2026-04-07: advisory: NVD publication date
  • 2026-04-16: kev added: Added to CISA Known Exploited Vulnerabilities catalog

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.