CVE-2026-45505: CWE-20 Improper Input Validation in Apache Software Foundation Apache ActiveMQ Broker
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.
AI Analysis
Technical Summary
This vulnerability in Apache ActiveMQ Broker arises from improper input validation allowing bypass of a prior fix. The Jolokia JMX-HTTP bridge exposed at /api/jolokia/ permits exec operations on all ActiveMQ MBeans, including methods that add network connectors and connectors. An authenticated attacker can craft a discovery URI that triggers the VM transport's brokerConfig parameter to load a remote Spring XML application context via ResourceXmlApplicationContext. Since Spring instantiates singleton beans before BrokerService validates configuration, this leads to arbitrary code execution through bean factory methods such as Runtime.exec(). The issue affects versions before 5.19.7 and from 6.0.0 before 6.2.6, with fixed versions available at 5.19.7 and 6.2.6.
Potential Impact
An authenticated attacker can achieve arbitrary code execution on the JVM running the Apache ActiveMQ Broker by exploiting this vulnerability. This could allow execution of malicious commands or code within the broker environment, potentially compromising the system hosting the broker. The vulnerability bypasses prior mitigations and affects multiple versions of Apache ActiveMQ Broker.
Mitigation Recommendations
A fix is available. Users should upgrade Apache ActiveMQ Broker to version 5.19.7 or 6.2.6 or later, which address this vulnerability. No other mitigation or temporary workaround is specified in the advisory. Patch status is confirmed by the vendor advisory recommending these versions.
CVE-2026-45505: CWE-20 Improper Input Validation in Apache Software Foundation Apache ActiveMQ Broker
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.
CVSS v3.1
Score 8.8high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in Apache ActiveMQ Broker arises from improper input validation allowing bypass of a prior fix. The Jolokia JMX-HTTP bridge exposed at /api/jolokia/ permits exec operations on all ActiveMQ MBeans, including methods that add network connectors and connectors. An authenticated attacker can craft a discovery URI that triggers the VM transport's brokerConfig parameter to load a remote Spring XML application context via ResourceXmlApplicationContext. Since Spring instantiates singleton beans before BrokerService validates configuration, this leads to arbitrary code execution through bean factory methods such as Runtime.exec(). The issue affects versions before 5.19.7 and from 6.0.0 before 6.2.6, with fixed versions available at 5.19.7 and 6.2.6.
Potential Impact
An authenticated attacker can achieve arbitrary code execution on the JVM running the Apache ActiveMQ Broker by exploiting this vulnerability. This could allow execution of malicious commands or code within the broker environment, potentially compromising the system hosting the broker. The vulnerability bypasses prior mitigations and affects multiple versions of Apache ActiveMQ Broker.
Mitigation Recommendations
A fix is available. Users should upgrade Apache ActiveMQ Broker to version 5.19.7 or 6.2.6 or later, which address this vulnerability. No other mitigation or temporary workaround is specified in the advisory. Patch status is confirmed by the vendor advisory recommending these versions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-05-12T16:18:34.151Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a1d4e75e29bf47b50cd4a0e
Added to database: 6/1/2026, 9:18:45 AM
Last enriched: 6/1/2026, 9:35:29 AM
Last updated: 6/2/2026, 5:06:06 AM
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.