VulnerabilityPublished 4 Nov 2026

CVE-2026-108946: Apache ActiveMQ · Improper Input Validation

Affects Apache ActiveMQSource CVE Database V5

Compare

Not known to be exploited : upgrade to 6.3.3 or 5.19.12 soon.

Data as of 4 Nov 2026, 12:28 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in 6.3.3, 5.19.12

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Apache ActiveMQ and ActiveMQ Broker and org.apache.activemq/apache-activemq and org.apache.activemq/activemq-broker to 6.3.3 or 5.19.12.

Affected software

Product	Affected	Fixed in
Apache ActiveMQorg.apache.activemq:apache-activemq	Affected >=6.0.0 <6.3.3	Fixed in 6.3.3
Apache ActiveMQorg.apache.activemq:apache-activemq	Affected <5.19.12	Fixed in 5.19.12
ActiveMQ Brokerorg.apache.activemq:activemq-broker	Affected >=6.0.0 <6.3.3	Fixed in 6.3.3
ActiveMQ Brokerorg.apache.activemq:activemq-broker	Affected <5.19.12	Fixed in 5.19.12
Mavenorg.apache.activemq/apache-activemq`pkg:maven/org.apache.activemq/apache-activemq`Other threats	Affected >=6.0.0 <6.3.3 <5.19.12	Fixed in 6.3.3 5.19.12
Mavenorg.apache.activemq/activemq-broker`pkg:maven/org.apache.activemq/activemq-broker`Other threats	Affected >=6.0.0 <6.3.3 <5.19.12	Fixed in 6.3.3 5.19.12

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache ActiveMQ and Apache ActiveMQ KahaDB to versions 6.3.3 or later, or 5.19.12 or later, where this vulnerability is fixed. No other mitigation or workaround is indicated by the vendor advisory.

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

An authenticated attacker can impersonate another user's connection and consumer IDs, allowing unauthorized access to temporary queues or topics, disruption of legitimate subscriptions by forcibly removing them, and deletion of in-flight messages that have not yet been acknowledged. This compromises message integrity and availability within the affected ActiveMQ broker instances.

Summary

Apache ActiveMQ and Apache ActiveMQ KahaDB contain an improper input validation vulnerability (CWE-20) where the broker resolves connection, session, and consumer state from user-provided IDs without sufficiently validating ownership. This allows an authenticated client to spoof another user's IDs, enabling unauthorized consumption from temporary queues/topics, disruption of victim subscriptions by removing or disconnecting them, and permanent deletion of unacknowledged messages through forged acknowledgments. The vulnerability affects Apache ActiveMQ versions >=6.0.0 <6.3.3 and versions <5.19.12. The issue is fixed in versions 6.3.3 and 5.19.12.

CWE-20Improper Input Validation (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #18OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Attack Surface Reduction
Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build "recognizers" for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of…
Architecture and Design · Libraries or Frameworks
Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Server Side Include (SSI) Injection (opens in a new tab)
Cross Zone Scripting (opens in a new tab)
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 10:30 UTC

WeaknessesCWE-20

Technical details

References

Community reviews

Related threats