CVE-2026-45505: Apache ActiveMQ code injection via Jolokia JMX-HTTP bridge bypass

CVE-2026-45505 · Severity: high · CVSS 8.8 · Published 2026-06-01

Apache ActiveMQ, a popular open-source message broker used for communication between different software applications, is vulnerable to a code injection flaw. An authenticated attacker can exploit this to run unauthorized commands on the server hosting the broker. This could lead to a full system takeover, data theft, or disruption of business operations.

Technologies: Apache ActiveMQ, 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-45505 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-45505 being exploited in the wild.
How severe is CVE-2026-45505?
High severity, with a CVSS score of 8.8, published 1 June 2026.
Which products and versions are affected?
Apache ActiveMQ < 5.19.7, 6.0.0 to < 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; org.apache.activemq:apache-activemq (Maven) ECOSYSTEM:introduced=0,fixed=5.19.7.
Is there a fix for CVE-2026-45505?
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-45505 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-45505?
Check whether you run Apache ActiveMQ, org.apache.activemq:activemq-all (Maven), org.apache.activemq:activemq-broker (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

This vulnerability is a bypass of the fix for CVE-2026-34197. Apache ActiveMQ exposes the Jolokia JMX-HTTP bridge at /api/jolokia/, which by default allows execution operations on ActiveMQ MBeans. An authenticated attacker can use non-parenthesized discovery wrappers (e.g., 'masterslave:vm://' or 'static:vm://') to bypass input validation. By crafting a discovery URI that triggers the VM transport's brokerConfig parameter, an attacker can force the application to load a remote Spring XML application context. Because Spring instantiates singleton beans before the BrokerService validates the configuration, an attacker can achieve arbitrary code execution via bean factory methods like Runtime.exec(). The issue is resolved in versions 5.19.7 and 6.2.6.

Affected products

  • Apache ActiveMQ Broker < 5.19.7, 6.0.0 to < 6.2.6
  • Apache ActiveMQ All < 5.19.7, 6.0.0 to < 6.2.6
  • Apache ActiveMQ < 5.19.7, 6.0.0 to < 6.2.6

Identifiers

  • CVE-2026-45505
  • GHSA-v853-w46p-fv2h

Timeline

  • 2026-06-01: advisory: Initial publication of the advisory
  • 2026-07-09: other: Advisory updated and reviewed by GitHub

References

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