CVE-2025-66168
Integer Overflow in Apache ActiveMQ MQTT Remaining Length Parsing
Publication date: 2026-03-04
Last updated on: 2026-04-10
Assigner: Apache Software Foundation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| apache | activemq | to 5.19.2 (exc) |
| apache | activemq | 6.2.0 |
| apache | activemq | From 6.0.0 (inc) to 6.1.8 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-190 | The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in Apache ActiveMQ involves improper validation of the Remaining Length field during the decoding of malformed MQTT packets. An integer overflow can occur, causing the broker to miscalculate the total Remaining Length and misinterpret the payload as multiple MQTT control packets. This leads to unexpected behavior when the broker interacts with non-compliant clients and violates the MQTT v3.1.1 specification.
How can this vulnerability impact me? :
The vulnerability can cause Apache ActiveMQ brokers to behave unexpectedly when processing MQTT packets from non-compliant clients. This may lead to incorrect handling of messages after authentication, potentially disrupting communication or causing instability in the message broker service.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, users are recommended to upgrade Apache ActiveMQ to version 5.19.2, 6.1.9, or 6.2.1, which contain fixes for this issue.
Note that brokers not enabling MQTT transport connectors are not impacted by this vulnerability.