Apache ActiveMQ, ActiveMQ Broker: The broker does not verify user provided connection id matches connection
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 6.3.3, 5.19.12
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 6.3.3, 5.19.12.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure?/25Exposure: unknown (data gap). No advisory context yet
- Reach10/20Affects Maven packages
- Severity?/10Severity: unknown (data gap). No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
CVE-2026-108946 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Apache ActiveMQ and ActiveMQ Broker; fixed in 6.3.3 and 5.19.12.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Fix
- Fixed in 6.3.3, 5.19.12
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apache ActiveMQ and ActiveMQ KahaDB brokers fail to check that connection IDs supplied by a client belong to that client, so an authenticated user can impersonate another connection to consume its temporary queue or topic, tear down its live subscription, or permanently delete an unacknowledged message. Exploitation requires the attacker to already have valid credentials, and no attacker-reachable network path is specified in the available data.
Read the original description
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.
Impact
- Widely used
4 packages depend on org.apache.activemq:apache-activemq.Source: deps.dev
What to do
Upgrade to a fixed version: 6.3.3, 5.19.12.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- org.apache.activemq:apache-activemqMaven
From 6.0.0 · fixed in 6.3.3; fixed in 5.19.12
- org.apache.activemq:activemq-brokerMaven
From 6.0.0 · fixed in 6.3.3; fixed in 5.19.12
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-108946
Is CVE-2026-108946 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-108946?
org.apache.activemq:apache-activemq (Maven): from 6.0.0 before 6.3.3; before 5.19.12. org.apache.activemq:activemq-broker (Maven): from 6.0.0 before 6.3.3; before 5.19.12.Source: cve.now feed data
How do I fix CVE-2026-108946?
Upgrade to a fixed version: 6.3.3, 5.19.12.Source: cve.now feed data