Staging Environment: Content and features may be unstable or change without notice.
Search for packages
Package details: pkg:maven/org.apache.activemq/apache-activemq@6.0.0
purl pkg:maven/org.apache.activemq/apache-activemq@6.0.0
Next non-vulnerable version 6.1.2
Latest non-vulnerable version 6.2.4
Risk 4.0
Vulnerabilities affecting this package (4)
Vulnerability Summary Fixed by
VCID-bktu-qch2-5ugv
Aliases:
CVE-2025-66168
GHSA-c825-6ph3-4h84
Apache ActiveMQ is Vulnerable to Integer Overflow or Wraparound 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.
6.1.9
Affected by 0 other vulnerabilities.
6.2.1
Affected by 0 other vulnerabilities.
VCID-cm77-qbk4-63ff
Aliases:
CVE-2026-39304
GHSA-5568-6qcg-g7fx
Apache ActiveMQ: Denial of Service via Out of Memory vulnerability Denial of Service via Out of Memory vulnerability in Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ. ActiveMQ NIO SSL transports do not correctly handle TLSv1.3 handshake KeyUpdates triggered by clients. This makes it possible for a client to rapidly trigger updates which causes the broker to exhaust all its memory in the SSL engine leading to DoS. Note: TLS versions before TLSv1.3 (such as TLSv1.2) are broken but are not vulnerable to OOM. Previous TLS versions require a full handshake renegotiation which causes a connection to hang but not OOM. This is fixed as well. This issue affects Apache ActiveMQ Client: before 5.19.4, from 6.0.0 before 6.2.4; Apache ActiveMQ Broker: before 5.19.4, from 6.0.0 before 6.2.4; Apache ActiveMQ: before 5.19.4, from 6.0.0 before 6.2.4. Users are recommended to upgrade to version 6.2.4 or 5.19.5, which fixes the issue.
6.2.4
Affected by 0 other vulnerabilities.
VCID-tyaw-6dpw-mudm
Aliases:
CVE-2026-40046
GHSA-xvqc-pp94-fmpx
Apache ActiveMQ, Apache ActiveMQ All, Apache ActiveMQ MQTT vulnerable to Integer Overflow or Wraparound Integer Overflow or Wraparound vulnerability in Apache ActiveMQ, Apache ActiveMQ All, Apache ActiveMQ MQTT. The fix for "CVE-2025-66168: MQTT control packet remaining length field is not properly validated" was only applied to 5.19.2 (and future 5.19.x) releases but was missed for all 6.0.0+ versions. This issue affects Apache ActiveMQ: from 6.0.0 before 6.2.4; Apache ActiveMQ All: from 6.0.0 before 6.2.4; Apache ActiveMQ MQTT: from 6.0.0 before 6.2.4. Users are recommended to upgrade to version 6.2.4 or a 5.19.x version starting with 5.19.2 or later (currently latest is 5.19.5), which fixes the issue.
6.2.4
Affected by 0 other vulnerabilities.
VCID-wema-7dnk-bkhy
Aliases:
CVE-2024-32114
GHSA-gj5m-m88j-v7c3
Apache ActiveMQ's default configuration doesn't secure the API web context In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located). It means that anyone can use these layers without any required authentication. Potentially, anyone can interact with the broker (using Jolokia JMX REST API) and/or produce/consume messages or purge/delete destinations (using the Message REST API). To mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement: <bean id="securityConstraintMapping" class="org.eclipse.jetty.security.ConstraintMapping">   <property name="constraint" ref="securityConstraint" />   <property name="pathSpec" value="/" /> </bean> Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.
6.1.2
Affected by 0 other vulnerabilities.
Vulnerabilities fixed by this package (0)
Vulnerability Summary Aliases
This package is not known to fix vulnerabilities.

Date Actor Action Vulnerability Source VulnerableCode Version
2026-04-16T22:57:00.164125+00:00 GitLab Importer Affected by VCID-wema-7dnk-bkhy https://gitlab.com/gitlab-org/advisories-community/-/blob/main/maven/org.apache.activemq/apache-activemq/CVE-2024-32114.yml 38.4.0
2026-04-13T07:05:09.624434+00:00 GHSA Importer Affected by VCID-cm77-qbk4-63ff https://github.com/advisories/GHSA-5568-6qcg-g7fx 38.3.0
2026-04-13T07:05:04.558207+00:00 GHSA Importer Affected by VCID-tyaw-6dpw-mudm https://github.com/advisories/GHSA-xvqc-pp94-fmpx 38.3.0
2026-04-13T07:05:01.901967+00:00 GHSA Importer Affected by VCID-bktu-qch2-5ugv https://github.com/advisories/GHSA-c825-6ph3-4h84 38.3.0
2026-04-12T00:15:16.108772+00:00 GitLab Importer Affected by VCID-wema-7dnk-bkhy https://gitlab.com/gitlab-org/advisories-community/-/blob/main/maven/org.apache.activemq/apache-activemq/CVE-2024-32114.yml 38.3.0
2026-04-03T00:22:02.784201+00:00 GitLab Importer Affected by VCID-wema-7dnk-bkhy https://gitlab.com/gitlab-org/advisories-community/-/blob/main/maven/org.apache.activemq/apache-activemq/CVE-2024-32114.yml 38.1.0
2026-04-02T12:39:06.333593+00:00 GitLab Importer Affected by VCID-wema-7dnk-bkhy https://gitlab.com/gitlab-org/advisories-community/-/blob/main/maven/org.apache.activemq/apache-activemq/CVE-2024-32114.yml 38.0.0
2026-04-01T16:08:21.676432+00:00 GHSA Importer Affected by VCID-bktu-qch2-5ugv https://github.com/advisories/GHSA-c825-6ph3-4h84 38.0.0
2026-04-01T16:05:11.882134+00:00 GHSA Importer Affected by VCID-wema-7dnk-bkhy https://github.com/advisories/GHSA-gj5m-m88j-v7c3 38.0.0