BIT-activemq-2025-66168

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/activemq/BIT-activemq-2025-66168.json
JSON Data
https://api.test.osv.dev/v1/vulns/BIT-activemq-2025-66168
Aliases
Published
2026-03-06T08:36:37.326Z
Modified
2026-03-08T23:11:16.546958Z
Summary
Apache ActiveMQ, Apache ActiveMQ All Module, Apache ActiveMQ MQTT Module: MQTT control packet remaining length field is not properly validated
Details

Apache ActiveMQ does not properly validate the remaining length field which may lead to an overflow during the decoding of malformed packets. When this integer overflow occurs, ActiveMQ may incorrectly compute the total Remaining Length and subsequently misinterpret the payload as multiple MQTT control packets which makes the broker susceptible to unexpected behavior when interacting with non-compliant clients. This behavior violates the MQTT v3.1.1 specification, which restricts Remaining Length to a maximum of 4 bytes. The scenario occurs on established connections after the authentication process. Brokers that are not enabling mqtt transport connectors are not impacted.

This issue affects Apache ActiveMQ: before 5.19.2, 6.0.0 to 6.1.8, and 6.2.0

Users are recommended to upgrade to version 5.19.2, 6.1.9, or 6.2.1, which fixes the issue.

Database specific
{
    "cpes": [
        "cpe:2.3:a:apache:activemq:*:*:*:*:*:maven:*:*"
    ],
    "severity": "High"
}
References

Affected packages

Bitnami / activemq

Package

Name
activemq
Purl
pkg:bitnami/activemq

Severity

  • 8.8 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.19.2
Introduced
6.0.0
Fixed
6.1.9
Introduced
6.2.0
Fixed
6.2.1

Database specific

source
"https://github.com/bitnami/vulndb/tree/main/data/activemq/BIT-activemq-2025-66168.json"