Apache ActiveMQ: Denial of Service via Out of Memory vulnerability
Published 10 Apr 2026 · Updated 10 Sept 2026
Is your project on an affected org.apache.activemq:activemq-client?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <5.19.4
- Fixed in
- 5.19.4
mvn versions:use-dep-version -Dincludes=org.apache.activemq:activemq-client -DdepVersion=5.19.4 -DforceVersion=true- Affected
- >=6.0.0 <6.2.4
- Fixed in
- 6.2.4
mvn versions:use-dep-version -Dincludes=org.apache.activemq:activemq-client -DdepVersion=6.2.4 -DforceVersion=true- Affected
- <5.19.4
- Fixed in
- 5.19.4
mvn versions:use-dep-version -Dincludes=org.apache.activemq:activemq-broker -DdepVersion=5.19.4 -DforceVersion=true- Affected
- >=6.0.0 <6.2.4
- Fixed in
- 6.2.4
mvn versions:use-dep-version -Dincludes=org.apache.activemq:activemq-broker -DdepVersion=6.2.4 -DforceVersion=true- Affected
- <5.19.4
- Fixed in
- 5.19.4
mvn versions:use-dep-version -Dincludes=org.apache.activemq:activemq-all -DdepVersion=5.19.4 -DforceVersion=true- Affected
- >=6.0.0 <6.2.4
- Fixed in
- 6.2.4
mvn versions:use-dep-version -Dincludes=org.apache.activemq:activemq-all -DdepVersion=6.2.4 -DforceVersion=true- Affected
- <5.19.4
- Fixed in
- 5.19.4
mvn versions:use-dep-version -Dincludes=org.apache.activemq:apache-activemq -DdepVersion=5.19.4 -DforceVersion=true- Affected
- >=6.0.0 <6.2.4
- Fixed in
- 6.2.4
mvn versions:use-dep-version -Dincludes=org.apache.activemq:apache-activemq -DdepVersion=6.2.4 -DforceVersion=trueDetails
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.
Is GHSA-5568-6qcg-g7fx in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.activemq:activemq-client, and gives you the command that fixes it.
More advisories for org.apache.activemq:activemq-client
- HighCVE-2026-50734Apache ActiveMQ Client, Apache ActiveMQ, Apache ActiveMQ All has a Memory Allocation with Excessive Size Value vulnerability · 30 Jun 2026
- HighCVE-2026-53917Apache ActiveMQ, Apache ActiveMQ All, Apache ActiveMQ Client, Apache ActiveMQ Broker have Memory Allocation with Excessive Size Value vulnerability · 30 Jun 2026
- MediumCVE-2026-33227Apache ActiveMQ: Improper validation and restriction of a classpath path name · 7 Apr 2026
- MediumCVE-2025-27533Apache ActiveMQ: Unchecked buffer length can cause excessive memory allocation · 7 May 2025
- CriticalCVE-2023-46604Apache ActiveMQ is vulnerable to Remote Code Execution · 27 Oct 2023
- MediumCVE-2013-3060Improper Authentication in Apache ActiveMQ · 17 May 2022
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.