GHSA-5568-6qcg-g7fx BIT-activemq-2026-39304 CVE-2026-39304
Apache ActiveMQ: Denial of Service via Out of Memory vulnerability
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.90%
- Chance of exploitation in the next 30 days. Higher than 59.56% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-400 Uncontrolled Resource Consumption
- Fix
- Available
- 4 packages have a fixed version
Description
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.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.apache.activemq:activemq-all | < 5.19.4 |
5.19.4 |
| org.apache.activemq:activemq-all | >= 6.0.0, < 6.2.4 |
6.2.4 |
| org.apache.activemq:activemq-broker | < 5.19.4 |
5.19.4 |
| org.apache.activemq:activemq-broker | >= 6.0.0, < 6.2.4 |
6.2.4 |
| org.apache.activemq:activemq-client | < 5.19.4 |
5.19.4 |
| org.apache.activemq:activemq-client | >= 6.0.0, < 6.2.4 |
6.2.4 |
| org.apache.activemq:apache-activemq | < 5.19.4 |
5.19.4 |
| org.apache.activemq:apache-activemq | >= 6.0.0, < 6.2.4 |
6.2.4 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
org.apache.activemq:activemq-all Maven → 5.19.4
- maven
<dependency><groupId>org.apache.activemq</groupId><artifactId>activemq-all</artifactId><version>5.19.4</version></dependency>- gradle
implementation("org.apache.activemq:activemq-all:5.19.4")
org.apache.activemq:activemq-broker Maven → 5.19.4
- maven
<dependency><groupId>org.apache.activemq</groupId><artifactId>activemq-broker</artifactId><version>5.19.4</version></dependency>- gradle
implementation("org.apache.activemq:activemq-broker:5.19.4")
org.apache.activemq:activemq-client Maven → 5.19.4
- maven
<dependency><groupId>org.apache.activemq</groupId><artifactId>activemq-client</artifactId><version>5.19.4</version></dependency>- gradle
implementation("org.apache.activemq:activemq-client:5.19.4")
org.apache.activemq:apache-activemq Maven → 5.19.4
- maven
<dependency><groupId>org.apache.activemq</groupId><artifactId>apache-activemq</artifactId><version>5.19.4</version></dependency>- gradle
implementation("org.apache.activemq:apache-activemq:5.19.4")
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Weakness
CWE-400: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How to prevent it
- Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
- Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
- Implementation: Ensure that all failures in resource allocation place the system into a safe posture.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-rxpj-7qvf-xv32 Authenticated Apache ActiveMQ Broker and Apache ActiveMQ users could perform RCE via Jolokia MBeans | High Known exploited | Also affects org.apache.activemq:activemq-all |
| GHSA-crg9-44h2-xw35 Apache ActiveMQ is vulnerable to Remote Code Execution | Critical Known exploited | Also affects org.apache.activemq:activemq-client |
| GHSA-rxqh-fc23-gxp2 Improper Input Validation in Apache ActiveMQ | Critical Known exploited | Also affects org.apache.activemq:activemq-client |
| GHSA-hf52-78x8-6w3w Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All have an Exposure of Sensitive Information Through Metadata vulnerability | Medium | Also affects org.apache.activemq:activemq-all |
| GHSA-99qx-5qqr-4j95 Apache ActiveMQ has an Incorrect Default Permissions vulnerability | High | Also affects org.apache.activemq:apache-activemq |
| GHSA-cpw7-g3p5-qrfq Apache ActiveMQ server has an incomplete authorization workflow | Medium | Also affects org.apache.activemq:apache-activemq |
| GHSA-v853-w46p-fv2h Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ have a Code Injection issue | High | Also affects org.apache.activemq:activemq-all |
| GHSA-hg6c-8mvr-jqc9 Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ have a Code Injection issue | High | Also affects org.apache.activemq:activemq-all |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor