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

CVE-2026-42588 · Severity: high · CVSS 8.1 · Published 2026-06-01

Apache ActiveMQ, a popular open-source message broker used for communication between different software applications, contains a vulnerability in its management console. An authenticated user can exploit a management interface to run unauthorized commands on the server. This could allow an attacker to take full control of the message broker, potentially leading to the theft of sensitive business data or disruption of message delivery services.

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

Quick answers

Is CVE-2026-42588 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-42588 being exploited in the wild.
How severe is CVE-2026-42588?
High severity, with a CVSS score of 8.1, published 1 June 2026.
Which products and versions are affected?
Apache ActiveMQ < 5.19.7, >= 6.0.0 < 6.2.6; Apache Activemq Broker < 5.19.7, >= 6.0.0 < 6.2.6; org.apache.activemq:activemq-all (Maven) ECOSYSTEM:introduced=0,fixed=5.19.7; org.apache.activemq:activemq-broker (Maven) ECOSYSTEM:introduced=0,fixed=5.19.7; and 1 more.
Is there a fix for CVE-2026-42588?
Yes. org.apache.activemq:activemq-all (Maven): upgrade to 5.19.7 or later; org.apache.activemq:activemq-broker (Maven): upgrade to 5.19.7 or later; org.apache.activemq:apache-activemq (Maven): upgrade to 5.19.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-42588 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-42588?
Check whether you run Apache ActiveMQ, Apache Activemq Broker, org.apache.activemq:activemq-all (Maven) 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.7 or later
    # set org.apache.activemq:activemq-all to 5.19.7 in your pom.xml or build.gradle
  • org.apache.activemq:activemq-broker (Maven): upgrade to 5.19.7 or later
    # set org.apache.activemq:activemq-broker to 5.19.7 in your pom.xml or build.gradle
  • org.apache.activemq:apache-activemq (Maven): upgrade to 5.19.7 or later
    # set org.apache.activemq:apache-activemq to 5.19.7 in your pom.xml or build.gradle

Technical details

Apache ActiveMQ Classic exposes the Jolokia JMX-HTTP bridge at /api/jolokia/ with a default policy that allows 'exec' operations on ActiveMQ MBeans. An authenticated attacker can invoke 'BrokerService.addNetworkConnector' using a crafted 'masterslave://' discovery URI. This URI triggers the VM transport's 'brokerConfig' parameter, which utilizes Spring's 'ResourceXmlApplicationContext' to load a remote XML configuration. Because Spring instantiates singleton beans before the broker validates the configuration, an attacker can achieve arbitrary code execution via bean factory methods (e.g., Runtime.exec). The vulnerability is patched in versions 5.19.7 and 6.2.6.

Affected products

  • Apache ActiveMQ Broker < 5.19.7, >= 6.0.0 < 6.2.6
  • Apache ActiveMQ All < 5.19.7, >= 6.0.0 < 6.2.6
  • Apache ActiveMQ < 5.19.7, >= 6.0.0 < 6.2.6

Identifiers

  • CVE-2026-42588
  • GHSA-hg6c-8mvr-jqc9

Timeline

  • 2026-05-31: disclosed: Initial disclosure on oss-security mailing list
  • 2026-06-01: advisory: GitHub and NVD advisories published
  • 2026-07-09: other: Advisory reviewed and updated

References

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