Who is not affected by CVE-2026-108946?

Q: Who is not affected by CVE-2026-108946?

Not affected if: patched-version, single-trusted-client, unauthenticated-only-access.

MEDIUMNOT SCORED

NO KNOWN
EXPLOIT

CVE-2026-108946 · Runtime

Apache ActiveMQ: authenticated clients can hijack other users' consumers and messages

NO FIX YET · SEE WHAT TO DO

Apache ActiveMQ does not always check that connection, session and consumer ids belong to the client using them. An authenticated client can consume from another connection's temporary queue, tear down a victim's subscription, or delete an unacknowledged message.

first public Nov 4, 2026 · 1 source

Is this in your stack? Find out in 2 minutes.

Tell InfraStack what you run. It checks this one, and every next one, against your stack.

Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.

InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.

In Slack

Run the check

01 · Who is affected

Any deployment of ActiveMQ or ActiveMQ KahaDB in the affected ranges where more than one client connects to the broker. An attacker needs valid broker credentials, so brokers limited to fully trusted clients carry less risk. Sources do not say whether default configurations are exposed.

Not affected if patched-version, single-trusted-client, unauthenticated-only-access

Who cares activemq, apache-activemq, java, message-broker

02 · How to check

Check the installed ActiveMQ version (activemq --version or the version in the broker's lib directory); versions from 6.0.0 before 6.3.3 and before 5.19.12 are affected.
Check whether the broker is reachable by clients you do not fully trust.

03 · The fix

Apache ActiveMQ 6.x: upgrade to 6.3.3 or later (6.4.0 recommended)
Apache ActiveMQ 5.x: upgrade to 5.19.12
Apache ActiveMQ KahaDB: same ranges as ActiveMQ, upgrade to 6.3.3, 6.4.0, or

Exploited: No reports yet
Public exploit: None on GitHub
EPSS: Not scored
Last updated: Nov 4, 2026

How it unfolded

1 events · Nov 4, 2026 → Nov 4, 2026

Nov 4, 202611:26 UTCNVD CVE-2026-108946

What the sources say, verbatim

1,047 characters

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.

Get the next one threat the day it hits your stack.

Start watching free

Post Share

MEDIUMNOT SCORED

NO KNOWN
EXPLOIT

CVE-2026-108946 · Runtime

Apache ActiveMQ: authenticated clients can hijack other users' consumers and messages

NO FIX YET · SEE WHAT TO DO

first public Nov 4, 2026 · 1 source

Is this in your stack? Find out in 2 minutes.

Tell InfraStack what you run. It checks this one, and every next one, against your stack.

Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.

InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.

In Slack

Run the check

01 · Who is affected

Not affected if patched-version, single-trusted-client, unauthenticated-only-access

Who cares activemq, apache-activemq, java, message-broker

02 · How to check

Check the installed ActiveMQ version (activemq --version or the version in the broker's lib directory); versions from 6.0.0 before 6.3.3 and before 5.19.12 are affected.
Check whether the broker is reachable by clients you do not fully trust.

03 · The fix

Apache ActiveMQ 6.x: upgrade to 6.3.3 or later (6.4.0 recommended)
Apache ActiveMQ 5.x: upgrade to 5.19.12
Apache ActiveMQ KahaDB: same ranges as ActiveMQ, upgrade to 6.3.3, 6.4.0, or

Exploited: No reports yet
Public exploit: None on GitHub
EPSS: Not scored
Last updated: Nov 4, 2026

How it unfolded

1 events · Nov 4, 2026 → Nov 4, 2026

Nov 4, 202611:26 UTCNVD CVE-2026-108946

What the sources say, verbatim

1,047 characters

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

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.

Get the next one threat the day it hits your stack.

Start watching free

Apache ActiveMQ: authenticated clients can hijack other users' consumers and messages

01 · Who is affected

02 · How to check

03 · The fix

How it unfolded

What the sources say, verbatim

Read next

Get the next one threat the day it hits your stack.

Apache ActiveMQ: authenticated clients can hijack other users' consumers and messages

01 · Who is affected

02 · How to check

03 · The fix

How it unfolded

What the sources say, verbatim

Read next

Get the next one threat the day it hits your stack.

Sources and references