# CVE-2026-108946: Apache ActiveMQ, ActiveMQ Broker: The broker does not verify user provided connection id matches connection

Status: published. Published: 2026-11-04. Updated: 2026-11-04.

Improper input validation vulnerability in Apache ActiveMQ, Apache ActiveMQ KahaDB.



The ActiveMQ broker resolves connection, session and consumer state from ids that are user provided and in some scenarios does not validate that they ids are bound to that user. This allows an authenticated client to spoof another user's ids. This allows:





  *   an authenticated client consumes from another connection's temporary queue/topic by putting the victim's connection id in its own ConsumerId, bypassing the broker-side ownership check. 
  *  a duplicate ConsumerId registration is only logged, after which the attacker's RemoveInfo or disconnect tears down the victim's live subscription
  *  a forged MessageAck for the victim's ConsumerId permanently deletes an in-flight, unacknowledged message.








This issue affects Apache ActiveMQ: from 6.0.0 before 6.3.3, before 5.19.12; Apache ActiveMQ KahaDB: from 6.0.0 before 6.3.3, before 5.19.12.



Users are recommended to upgrade to version 6.4.0, 6.3.3, or 5.19.12, which fixes the issue.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Apache Software Foundation / Apache ActiveMQ (org.apache.activemq:apache-activemq): ≥ 6.0.0; < 6.3.3 (affected, semver); ≥ 0; < 5.19.12 (affected, semver). Source: CNA: apache
- Apache Software Foundation / ActiveMQ Broker (org.apache.activemq:activemq-broker): ≥ 6.0.0; < 6.3.3 (affected, semver); ≥ 0; < 5.19.12 (affected, semver). Source: CNA: apache

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-20

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://lists.apache.org/thread/0spj0m846vhw3cjyfmzsy3l8vxh6f5t6 (CNA: apache; vendor-advisory)

- http://www.openwall.com/lists/oss-security/2026/11/03/17 (ADP: CVE)

- https://lists.apache.org/thread/0spj0m846vhw3cjyfmzsy3l8vxh6f5t6 (security@apache.org)

## Provenance

- CNA: apache: https://www.cve.org/CVERecord?id=CVE-2026-108946; retrieved 2026-11-04; source updated 2026-11-04

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-108946; retrieved 2026-11-04; source updated 2026-11-04

Revision: 2fa686389cd7ebe033236dce4889f4b59124cfa8dec49ad8aa9e705791b8a711

Canonical: https://y2.dev/cve/CVE-2026-108946

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.