---
id: CVE-2026-108946
title: >-
  Apache ActiveMQ, ActiveMQ Broker: The broker does not verify user provided
  connection id matches connection
summary: >-
  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 …
severity: none
cwe:
  - CWE-20
vendor: Apache Software Foundation
product: 'org.apache.activemq:apache-activemq'
affected:
  - 'org.apache.activemq:apache-activemq >= 6.0.0 < 6.3.3'
  - 'org.apache.activemq:apache-activemq < 5.19.12'
  - 'org.apache.activemq:activemq-broker >= 6.0.0 < 6.3.3'
  - 'org.apache.activemq:activemq-broker < 5.19.12'
published: '2026-11-04'
updated: '2026-11-04'
sourceUpdated: '2026-11-04T12:11:22.685Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-108946'
references:
  - url: 'https://lists.apache.org/thread/0spj0m846vhw3cjyfmzsy3l8vxh6f5t6'
tags:
  - cve.org
ingestedAt: '2026-11-05T20:33:06.729Z'
---

## Overview

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.

## Affected

- `org.apache.activemq:apache-activemq >= 6.0.0 < 6.3.3`
- `org.apache.activemq:apache-activemq < 5.19.12`
- `org.apache.activemq:activemq-broker >= 6.0.0 < 6.3.3`
- `org.apache.activemq:activemq-broker < 5.19.12`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.