CVE-2026-41044: Apache ActiveMQ, Apache ActiveMQ Broker, Apache ActiveMQ All: Authenticated user can perform RCE via DestinationView MBean exposed by Jolokia
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-41044 lets an authenticated attacker turn Apache ActiveMQ administration features into remote code execution on the broker server. The issue requires access to the admin web console/Jolokia path, but successful exploitation can compromise confidentiality, integrity, and availability of the messaging broker.
Executive priority
Treat as high priority for any ActiveMQ broker that is externally reachable, business-critical, or administered by many users. Patch promptly because compromise would execute code inside the broker JVM and could disrupt messaging-dependent services.
Technical view
Affected ActiveMQ versions allow a malicious broker name to bypass validation and include an xbean binding. Through the DestinationView MBean exposed by Jolokia, a message can trigger VM transport creation and load a remote Spring XML context, causing singleton bean instantiation before broker configuration validation.
Likely exposure
Exposure is most likely where Apache ActiveMQ admin web console or Jolokia is reachable by authenticated users and versions are before 5.19.6 or from 6.0.0 before 6.2.5.
Exploitation context
The source bundle reports no CISA KEV listing and provides no cited evidence of active exploitation. Exploitation requires authenticated access but has network attack vector, low complexity, no user interaction, and high impact across confidentiality, integrity, and availability.
Researcher notes
Key conditions are authenticated access, admin console/Jolokia reachability, DestinationView MBean availability, and affected version range. The public source describes the chain but does not provide proof of exploitation in the wild.
Mitigation direction
Upgrade Apache ActiveMQ to 6.2.5 or 5.19.6.
Prioritize brokers with reachable admin web console or Jolokia endpoints.
Limit admin web console and Jolokia access to trusted administrators only.
Review ActiveMQ administrative accounts for least privilege and unnecessary access.
Check vendor guidance for any environment-specific hardening notes.
Validation and detection
Inventory Apache ActiveMQ, activemq-broker, and activemq-all versions.
Confirm no affected version remains below 5.19.6 or between 6.0.0 and 6.2.4.
Verify admin web console and Jolokia are not broadly reachable.
Review authentication records for unexpected administrative access.
Confirm package dependencies match the fixed ActiveMQ release line.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
3ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-20 · source CWE mapping
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.