On this page

Atomicorp WAF Research Note: CVE-2026-45505

Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Jolokia addNetworkConnector Discovery Wrapper Bypass

CVE Details

Status: Attack Blocked by Atomicorp
Technical CPE data

This section lists vulnerable CPE matches retained from the NVD configurations. It supplements the readable affected-product information above.

  • cpe:2.3:a:apache:activemq:*:*:*:*:*:*:*:*
    • Version end (exclusive): 5.19.7
    • NVD match criteria ID: 793E68E6-9024-4518-B062-42B2DE5BB555
  • cpe:2.3:a:apache:activemq:*:*:*:*:*:*:*:*
    • Version start (inclusive): 6.0.0
    • Version end (exclusive): 6.2.6
    • NVD match criteria ID: FFF44DB9-1850-4B5F-AD0F-55CB5219AB22
  • cpe:2.3:a:apache:activemq_broker:*:*:*:*:*:*:*:*
    • Version end (exclusive): 5.19.7
    • NVD match criteria ID: FE27E832-0E65-4D05-A2EE-271152799E96
  • cpe:2.3:a:apache:activemq_broker:*:*:*:*:*:*:*:*
    • Version start (inclusive): 6.0.0
    • Version end (exclusive): 6.2.6
    • NVD match criteria ID: 94F0DB6E-BEF4-4BEB-92F5-3A7B65172CC2

Vulnerability Description

Improper Input Validation, Improper Control of Generation of Code (‘Code Injection’) vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ.

Non-parenthesized discovery wrappers such as masterslave:vm://...,... and static:vm://... incorrectly pass validation allowing bypass of fix in CVE-2026-34197. 

Original description from CVE-2026-34197.

Apache ActiveMQ exposes the Jolokia JMX-HTTP bridge at /api/jolokia/ on the web console. The default Jolokia access policy permits exec operations on all ActiveMQ MBeans (org.apache.activemq:*), including BrokerService.addNetworkConnector(String) and BrokerService.addConnector(String). An authenticated attacker can invoke these operations with a crafted discovery UR that triggers 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(). This issue affects Apache ActiveMQ Broker: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ All: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ: before 5.19.7, from 6.0.0 before 6.2.6.

Users are recommended to upgrade to version 5.19.7 or 6.2.6, which fixes the issue.

  1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (340014 , 340023 , 340029 , 344360 , 344361 , 344363 , 344364 , 344366 , 344370 , 393655 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

    • Affected versions: Apache Software Foundation Apache ActiveMQ Broker versions earlier than 5.19.7.
    • Affected versions: Apache Software Foundation Apache ActiveMQ Broker versions earlier than 6.2.6.
    • Affected versions: Apache Software Foundation Apache ActiveMQ All versions earlier than 5.19.7.
    • Affected versions: Apache Software Foundation Apache ActiveMQ All versions earlier than 6.2.6.
    • Affected versions: Apache Software Foundation Apache ActiveMQ versions earlier than 5.19.7.
    • Affected versions: Apache Software Foundation Apache ActiveMQ versions earlier than 6.2.6.
    • Recommended upgrade: Upgrade Apache Software Foundation Apache ActiveMQ Broker to 5.19.7 or later.
    • Recommended upgrade: Upgrade Apache Software Foundation Apache ActiveMQ Broker to 6.2.6 or later.
    • Recommended upgrade: Upgrade Apache Software Foundation Apache ActiveMQ All to 5.19.7 or later.
    • Recommended upgrade: Upgrade Apache Software Foundation Apache ActiveMQ All to 6.2.6 or later.
    • Recommended upgrade: Upgrade Apache Software Foundation Apache ActiveMQ to 5.19.7 or later.
    • Recommended upgrade: Upgrade Apache Software Foundation Apache ActiveMQ to 6.2.6 or later.

  3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

  • Source: Atomicorp AI Research Framework
  • Tags: cve, derived, rce, waf-probe

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ .