CVE-2026-108946: Apache ActiveMQ broker does not verify user provided connection ID (CVE-2026-108946)
User provided connection IDs are not validated against bound connection state in versions before 6.3.3 and 5.19.12.
Connection ID Spoofing in Apache ActiveMQ before 6.3.3 and 5.19.12
Improper input validation in Apache ActiveMQ allows authenticated clients to spoof connection, session, and consumer IDs. By inserting a victim's connection ID into its own ConsumerId, an attacker can consume from another user's temporary queues or topics, tear down subscriptions, and delete unacknowledged messages. This affects Apache ActiveMQ and ActiveMQ KahaDB versions 6.0.0 before 6.3.3 and before 5.19.12.
What to do: Upgrade to Apache ActiveMQ 6.4.0, 6.3.3, or 5.19.12.
| Product | Affected | Fixed in |
|---|---|---|
| Apache ActiveMQ | 6.0.0 before 6.3.3, before 5.19.12 | 6.4.0, 6.3.3, or 5.19.12 |
| Apache ActiveMQ KahaDB | 6.0.0 before 6.3.3, before 5.19.12 | 6.4.0, 6.3.3, or 5.19.12 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
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.
User provided connection IDs are not validated against bound connection state in versions before 6.3.3 and 5.19.12.
Today 1.6K readers · 2.4K views · 775 reads · all time 189K views