CVE-2026-50750: Apache ActiveMQ Denial of Service via Out of Memory

CVE-2026-50750 · Severity: high · CVSS 7.5 · Published 2026-06-30

Apache ActiveMQ, a popular open-source message broker used for communication between different software applications, is vulnerable to a denial-of-service attack. An unauthenticated attacker can repeatedly send specific commands that exhaust the server's memory, causing the broker to crash. This results in a complete service outage, preventing applications from exchanging messages and potentially disrupting business operations.

Technologies: Apache ActiveMQ, org.apache.activemq:activemq-all (Maven), org.apache.activemq:activemq-broker (Maven), org.apache.activemq:apache-activemq (Maven). Vendors: Apache, Maven.

Quick answers

Is CVE-2026-50750 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-50750 being exploited in the wild.
How severe is CVE-2026-50750?
High severity, with a CVSS score of 7.5, published 30 June 2026.
Which products and versions are affected?
Apache ActiveMQ 5.19.7 to 5.19.8, 6.2.6 to 6.2.7; org.apache.activemq:activemq-all (Maven) = 5.19.7, ECOSYSTEM:introduced=5.19.7,fixed=5.19.8; org.apache.activemq:activemq-broker (Maven) = 5.19.7, ECOSYSTEM:introduced=5.19.7,fixed=5.19.8; org.apache.activemq:apache-activemq (Maven) = 5.19.7, ECOSYSTEM:introduced=5.19.7,fixed=5.19.8.
Is there a fix for CVE-2026-50750?
Yes. org.apache.activemq:activemq-all (Maven): upgrade to 5.19.8 or later; org.apache.activemq:activemq-broker (Maven): upgrade to 5.19.8 or later; org.apache.activemq:apache-activemq (Maven): upgrade to 5.19.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-50750 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-50750?
Check whether you run Apache ActiveMQ, org.apache.activemq:activemq-all (Maven), org.apache.activemq:activemq-broker (Maven) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.apache.activemq:activemq-all (Maven): upgrade to 5.19.8 or later
    # set org.apache.activemq:activemq-all to 5.19.8 in your pom.xml or build.gradle
  • org.apache.activemq:activemq-broker (Maven): upgrade to 5.19.8 or later
    # set org.apache.activemq:activemq-broker to 5.19.8 in your pom.xml or build.gradle
  • org.apache.activemq:apache-activemq (Maven): upgrade to 5.19.8 or later
    # set org.apache.activemq:apache-activemq to 5.19.8 in your pom.xml or build.gradle

Technical details

A Denial of Service (DoS) vulnerability exists in Apache ActiveMQ due to improper resource management when handling BrokerInfo commands. An unauthenticated remote attacker can exploit this by repeatedly sending BrokerInfo commands without initiating a ConnectionInfo sequence. This behavior leads to an Out of Memory (OOM) condition, causing the broker process to crash. This issue emerged as a regression following the fix for CVE-2026-49270. The vulnerability is addressed in version 6.2.7.

Affected products

  • Apache ActiveMQ Broker 5.19.7 to 5.19.8, 6.2.6 to 6.2.7
  • Apache ActiveMQ 5.19.7 to 5.19.8, 6.2.6 to 6.2.7
  • Apache ActiveMQ All 5.19.7 to 5.19.8, 6.2.6 to 6.2.7

Identifiers

  • CVE-2026-50750
  • BIT-ACTIVEMQ-2026-50750
  • GHSA-9qj4-v6r6-3wmx

Timeline

  • 2026-06-30: disclosed
  • 2026-06-30: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.