CVE-2026-40466: Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Possible bypass of CVE-2026-34197 via HTTP discovery second-stage URI
Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ.
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().
This issue affects 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; Apache ActiveMQ: before 5.19.6, from 6.0.0 before 6.2.5.
Users are recommended to upgrade to version 5.19.6 or 6.2.5, which fixes the issue.
Security readout for executives and security teams
Plain-English summary
CVE-2026-40466 can let a logged-in attacker turn Apache ActiveMQ broker management access into code execution on the broker server. It is a bypass of an earlier fix and depends on Jolokia management exposure plus the activemq-http module being available. Apache recommends upgrading affected deployments.
Executive priority
Treat this as a high-priority server-side remediation for ActiveMQ environments. It can lead to code execution on messaging infrastructure, but available sources indicate authentication is required and do not confirm active exploitation.
Technical view
The issue affects Apache ActiveMQ Broker, All, and Apache ActiveMQ before 5.19.6, and 6.0.0 before 6.2.5. An authenticated attacker may bypass CVE-2026-34197 validation through HTTP Discovery transport, causing Spring ResourceXmlApplicationContext bean instantiation before BrokerService validation and resulting in JVM-level arbitrary code execution.
Likely exposure
Highest exposure is ActiveMQ brokers on vulnerable versions where Jolokia management actions are reachable by authenticated users and activemq-http is on the classpath. Internet-facing or broadly accessible broker management interfaces increase business urgency.
Exploitation context
The source bundle does not show KEV listing or confirmed active exploitation. The described path requires authentication, but the CVSS vector rates network attack complexity low with high confidentiality, integrity, and availability impact.
Researcher notes
Focus validation on version, Jolokia reachability, authenticated management permissions, and activemq-http presence. Evidence is limited to the published CVE data and linked advisories; no public exploit activity is established in the provided sources.
Mitigation direction
Upgrade Apache ActiveMQ to 5.19.6 or 6.2.5.
Prioritize brokers with reachable Jolokia management interfaces.
Restrict broker management access to trusted administrators while upgrading.
Check Apache and Red Hat guidance for environment-specific instructions.
Review whether activemq-http is present where it is not needed.
Validation and detection
Inventory ActiveMQ Broker, All, and Apache ActiveMQ package versions.
Confirm whether versions are before 5.19.6 or 6.0.0 through 6.2.4.
Identify brokers exposing Jolokia or remote management paths.
Check whether activemq-http is on the runtime classpath.
Verify upgraded systems report 5.19.6, 6.2.5, or later.
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
2ADP 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.
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
ADP timelineredhat-SADP
Made public.
Apr 24, 2026, 10:15 UTC (UTC+00:00)
CVE publishedCVE Program
The CVE record was published.
Apr 24, 2026, 10:15 UTC (UTC+00:00)
ADP timelineredhat-SADP
Reported to Red Hat.
Apr 24, 2026, 11:01 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Jul 15, 2026, 01:00 UTC (UTC+00:00)
ADP provider summaries
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPorg.apache.activemq/activemq-all: org.apache.activemq/activemq-broker: Apache ActiveMQ: Arbitrary code execution via improper input validation in HTTP Discovery transport