CVE-2026-50750: Denial of Service via Out of Memory in Apache Software Foundation Apache ActiveMQ Broker
Denial of Service via Out of Memory vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All. Following the fix for CVE-2026-49270 an unauthenticated attacker can now cause broker OOM by sending an repeated BrokerInfo commands without sending a ConnectionInfo, until the broker will crash with OOM. This issue affects Apache ActiveMQ Broker: from 5.19.7 before 5.19.8, from 6.2.6 before 6.2.7; Apache ActiveMQ: from 5.19.7 before 5.19.8, from 6.2.6 before 6.2.7; Apache ActiveMQ All: from 5.19.7 before 5.19.8, from 6.2.6 before 6.2.7. Users are recommended to upgrade to version 6.2.7, which fixes the issue.
AI Analysis
Technical Summary
Following the fix for CVE-2026-49270, Apache ActiveMQ Broker versions 5.19.7 up to but not including 5.19.8, and 6.2.6 up to but not including 6.2.7, are vulnerable to a denial of service via out-of-memory condition. An unauthenticated attacker can repeatedly send BrokerInfo commands without sending a ConnectionInfo, causing the broker to consume excessive memory until it crashes. This vulnerability is classified under CWE-400 (Uncontrolled Resource Consumption). The CVSS v3.1 base score is 7.5, indicating high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and impact limited to availability.
Potential Impact
Successful exploitation results in denial of service by crashing the Apache ActiveMQ Broker due to out-of-memory conditions. There is no impact on confidentiality or integrity, but availability is severely affected, potentially disrupting messaging services relying on the broker.
Mitigation Recommendations
A fix is available in Apache ActiveMQ Broker version 6.2.7. Users should upgrade to version 6.2.7 or later to remediate this vulnerability. No other mitigation or temporary workaround is indicated in the available data.
CVE-2026-50750: Denial of Service via Out of Memory in Apache Software Foundation Apache ActiveMQ Broker
Description
Denial of Service via Out of Memory vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All. Following the fix for CVE-2026-49270 an unauthenticated attacker can now cause broker OOM by sending an repeated BrokerInfo commands without sending a ConnectionInfo, until the broker will crash with OOM. This issue affects Apache ActiveMQ Broker: from 5.19.7 before 5.19.8, from 6.2.6 before 6.2.7; Apache ActiveMQ: from 5.19.7 before 5.19.8, from 6.2.6 before 6.2.7; Apache ActiveMQ All: from 5.19.7 before 5.19.8, from 6.2.6 before 6.2.7. Users are recommended to upgrade to version 6.2.7, which fixes the issue.
CVSS v3.1
Score 7.5high
Affected software
pkg:maven/Apache Software Foundation/org.apache.activemq:activemq-brokerpkg:maven/Apache Software Foundation/org.apache.activemq:apache-activemqpkg:maven/Apache Software Foundation/org.apache.activemq:activemq-allRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Following the fix for CVE-2026-49270, Apache ActiveMQ Broker versions 5.19.7 up to but not including 5.19.8, and 6.2.6 up to but not including 6.2.7, are vulnerable to a denial of service via out-of-memory condition. An unauthenticated attacker can repeatedly send BrokerInfo commands without sending a ConnectionInfo, causing the broker to consume excessive memory until it crashes. This vulnerability is classified under CWE-400 (Uncontrolled Resource Consumption). The CVSS v3.1 base score is 7.5, indicating high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and impact limited to availability.
Potential Impact
Successful exploitation results in denial of service by crashing the Apache ActiveMQ Broker due to out-of-memory conditions. There is no impact on confidentiality or integrity, but availability is severely affected, potentially disrupting messaging services relying on the broker.
Mitigation Recommendations
A fix is available in Apache ActiveMQ Broker version 6.2.7. Users should upgrade to version 6.2.7 or later to remediate this vulnerability. No other mitigation or temporary workaround is indicated in the available data.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-06-06T19:20:20.134Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a439fbb27e9c797199c07ca
Added to database: 06/30/2026, 10:51:39 UTC
Last enriched: 07/07/2026, 11:59:17 UTC
Last updated: 08/14/2026, 00:41:13 UTC
Views: 178
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.