CVE-2026-41044: Apache ActiveMQ code injection in admin web console

CVE-2026-41044 · Severity: high · CVSS 8.8 · Published 2026-04-24

Apache ActiveMQ, a popular open-source message broker, is vulnerable to a security flaw that allows an authenticated user to execute unauthorized commands on the server. By providing a specially crafted name for a broker through the administration console, an attacker can force the system to load and run malicious code from a remote location. This could result in a full system takeover, data theft, or disruption of message-processing 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-41044 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-41044 being exploited in the wild.
How severe is CVE-2026-41044?
High severity, with a CVSS score of 8.8, published 24 April 2026.
Which products and versions are affected?
Apache ActiveMQ < 5.19.6, 6.0.0 to < 6.2.5; Apache Activemq Broker < 5.19.6, 6.0.0 to < 6.2.5; org.apache.activemq:activemq-all (Maven) ECOSYSTEM:introduced=0,fixed=5.19.6; org.apache.activemq:activemq-broker (Maven) ECOSYSTEM:introduced=0,fixed=5.19.6; and 1 more.
Is there a fix for CVE-2026-41044?
Yes. org.apache.activemq:activemq-all (Maven): upgrade to 5.19.6 or later; org.apache.activemq:activemq-broker (Maven): upgrade to 5.19.6 or later; org.apache.activemq:apache-activemq (Maven): upgrade to 5.19.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41044 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-41044?
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.6 or later
    # set org.apache.activemq:activemq-all to 5.19.6 in your pom.xml or build.gradle
  • org.apache.activemq:activemq-broker (Maven): upgrade to 5.19.6 or later
    # set org.apache.activemq:activemq-broker to 5.19.6 in your pom.xml or build.gradle
  • org.apache.activemq:apache-activemq (Maven): upgrade to 5.19.6 or later
    # set org.apache.activemq:apache-activemq to 5.19.6 in your pom.xml or build.gradle

Technical details

An authenticated attacker with access to the admin web console can bypass input validation to set a malicious broker name containing an xbean binding. By subsequently using the DestinationView MBean to trigger a VM transport creation, the attacker forces the broker to load a remote Spring XML application context. Because Spring's ResourceXmlApplicationContext instantiates singleton beans before the BrokerService validates the configuration, an attacker can achieve arbitrary code execution (RCE) within the broker's JVM using bean factory methods like Runtime.exec(). The vulnerability is fixed in versions 5.19.6 and 6.2.5.

Affected products

  • Apache ActiveMQ < 5.19.6, 6.0.0 to < 6.2.5
  • Apache ActiveMQ Broker < 5.19.6, 6.0.0 to < 6.2.5
  • Apache ActiveMQ All < 5.19.6, 6.0.0 to < 6.2.5

Identifiers

  • CVE-2026-41044
  • GHSA-mr6m-xj7v-3cv3

Timeline

  • 2026-04-23: disclosed: Initial disclosure on oss-security mailing list
  • 2026-04-24: advisory: NVD and vendor advisory published

References

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