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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2026-41044)

The version of Apache ActiveMQ running on the remote host is prior to 5.19.6 or 6.x prior to 6.2.5. It is, therefore, affected by multiple vulnerabilities:

  - An authenticated attacker may bypass the fix in CVE-2026-34197 by adding a connector using an HTTP Discovery     transport via BrokerView.addNetworkConnector or BrokerView.addConnector through Jolokia if the activemq-http module     is on the classpath. A malicious HTTP endpoint can return a VM transport through the HTTP URI which will bypass the     validation added in CVE-2026-34197. The attacker can then use the VM transport's brokerConfig parameter to load a     remote Spring XML application context using ResourceXmlApplicationContext. 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().
    (CVE-2026-40466)

  - 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(). (CVE-2026-41044)

  - An authenticated attacker can show malicious content when browsing queues in the web console by overriding the     content type to be HTML (instead of XML) and by injecting HTML into a JMS selector field. (CVE-2026-41043)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2026-41044)

  - 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. (CVE-2026-41044)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Severity
441135	SCA: security update for org.apache.activemq:activemq-all, org.apache.activemq:activemq-broker, org.apache.activemq:apache-activemq (GHSA-mr6m-xj7v-3cv3)	Tenable Cloud Security	SCA Checks	high
441135	SCA: security update for org.apache.activemq:activemq-all, org.apache.activemq:activemq-broker, org.apache.activemq:apache-activemq (GHSA-mr6m-xj7v-3cv3)	Tenable Self-Hosted Container Security	SCA Checks	high
311265	Apache ActiveMQ < 5.19.6 / 6.x < 6.2.5 Multiple Vulnerabilities	Nessus	CGI abuses	high
310128	Linux Distros Unpatched Vulnerability : CVE-2026-41044	Nessus	Misc.	high

Detections

Analytics

CVE-2026-41044

high

Tenable Plugins

high

high

high

high