Apache ActiveMQ Allow Attackers to Trigger DoS Attacks With Malformed Packets
A vulnerability identified in Apache ActiveMQ (CVE-2025-66168, CVSS 5.4) permits authenticated attackers to initiate a Denial-of-Service (DoS) attack by exploiting malformed network packets.
A vulnerability identified in Apache ActiveMQ (CVE-2025-66168, CVSS 5.4) permits authenticated attackers to initiate a Denial-of-Service (DoS) attack by exploiting malformed network packets.
The vulnerability was discovered by researcher Gai Tanaka and corroborated by Apache maintainers Christopher L. Shannon and Matt Pavlovich. It originates in the Apache ActiveMQ MQTT module. Specifically, the issue arises when a client sends an MQTT control packet, and the broker reads a "remaining length" field to determine the subsequent data size.
The improper validation of this field leads to an integer overflow during the decoding process. This results in the broker miscalculating the payload size and misinterpreting a single malicious payload as multiple MQTT packets. This behavior contradicts the MQTT v3.1.1 specification, which limits the remaining length to four bytes, causing unexpected broker behavior and disrupting message handling.
The potential for exploitation is limited, as it requires the attacker to have an authenticated connection. Additionally, only servers with MQTT transport connectors enabled are susceptible. Servers without this feature remain unaffected.
The vulnerability was discovered by researcher Gai Tanaka and corroborated by Apache maintainers Christopher L.
The vulnerability affects the Apache ActiveMQ framework, the ActiveMQ All module, and the MQTT module across several versions:
All versions before 5.19.2 Versions 6.0.0 through 6.1.8 Version 6.2.0
Administrators are advised to upgrade to the patched versions: 5.19.2, 6.1.9, or 6.2.1. These updates address the issue by introducing strict validation checks on packet-length fields. If upgrading is not currently feasible, disabling the MQTT transport connector can serve as a temporary mitigation measure.
For further technical information, please refer to the official Apache ActiveMQ portal or consult the CVE tracking database.
Based on reporting by Cyber Security News.
