Answer in brief
CVE-2026-108946 records a Unknown severity vulnerability in Apache ActiveMQ, ActiveMQ Broker: The broker does not verify user provided connection id matches connection. The current sources do not mark it as known exploited. The current feed maps Apache Software Foundation/org.apache.activemq:activemq-broker (generic), Apache Software Foundation/org.apache.activemq:apache-activemq (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Apache Software Foundation/org.apache.activemq:activemq-broker (generic), Apache Software Foundation/org.apache.activemq:apache-activemq (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Apache Software Foundation/org.apache.activemq:activemq-brokergeneric | >=6.0.0 <6.3.3 || >=0 <5.19.12 | 6.3.3, 5.19.12 |
| Apache Software Foundation/org.apache.activemq:apache-activemqgeneric | >=6.0.0 <6.3.3 || >=0 <5.19.12 | 6.3.3, 5.19.12 |
Published upstream
Nov 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.