cbcvebase.
CVE-2026-41044
published 2026-04-24

CVE-2026-41044: Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ, Apache ActiveMQ Broker, Apache ActiveMQ…

PriorityP260high8.8CVSS 3.1
AVNACLPRLUINSUCHIHAH
EPSS
0.98%
58.6th percentile
Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ, Apache ActiveMQ Broker, Apache ActiveMQ All. An authenticated attacker can use the admin web console page to construct a malicious broker name that bypasses name validation to include an xbean binding that can be later used by a VM transport to load a remote Spring XML application. The attacker can then use the DestinationView mbean to send a message to trigger a VM transport creation that will reference this malicious broker name which can lead to loading the malicious Spring XML context file. 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: before 5.19.6, from 6.0.0 before 6.2.5; Apache ActiveMQ Broker: before 5.19.6, from 6.0.0 before 6.2.5; Apache ActiveMQ All: before 5.19.6, from 6.0.0 before 6.2.5. Users are recommended to upgrade to version 6.2.5 or 5.19.6, which fixes the issue.

Affected

10 ranges
VendorProductVersion rangeFixed in
apacheactivemq< 5.19.65.19.6
apacheactivemq>= 6.0.0 < 6.2.56.2.5
apacheactivemq_broker< 5.19.65.19.6
apacheactivemq_broker>= 6.0.0 < 6.2.56.2.5
apache_software_foundationapache_activemq< 5.19.65.19.6
apache_software_foundationapache_activemq>= 6.0.0 < 6.2.56.2.5
apache_software_foundationapache_activemq_all< 5.19.65.19.6
apache_software_foundationapache_activemq_all>= 6.0.0 < 6.2.56.2.5
apache_software_foundationapache_activemq_broker< 5.19.65.19.6
apache_software_foundationapache_activemq_broker>= 6.0.0 < 6.2.56.2.5

Detection & IOCsextracted from sources · hover to see the quote

  • Attacker uses the admin web console to set a malicious broker name containing an xbean binding, which is later used by a VM transport to load a remote Spring XML application context
  • Monitor use of the DestinationView MBean to send messages that trigger VM transport creation referencing a crafted broker name — this is the trigger mechanism for loading the malicious Spring XML context
  • Arbitrary code execution occurs via Spring bean factory methods such as Runtime.exec() — monitor for unexpected child process spawning from the ActiveMQ broker JVM process
  • Alert on outbound HTTP/HTTPS connections from the ActiveMQ broker JVM process to remote hosts, which may indicate loading of a remote Spring XML application context file
  • ·Exploitation requires an authenticated user account with access to the ActiveMQ admin web console — unauthenticated attackers cannot trigger this vulnerability
  • ·Affected versions: Apache ActiveMQ before 5.19.6 and from 6.0.0 before 6.2.5; fixed in 6.2.5 or 5.19.6
  • ·The root cause is that Spring's ResourceXmlApplicationContext instantiates all singleton beans before BrokerService validates the configuration, meaning malicious beans execute before any broker-level check can intervene

CVSS provenance

nvdv3.18.8HIGHCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vendor_redhat8.8HIGH
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.