CVE-2026-49432: Apache ActiveMQ denial of service in STOMP connector

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

Apache ActiveMQ, a widely used message broker for enterprise applications, is vulnerable to a denial-of-service attack. An unauthenticated remote attacker can send specially crafted messages to the STOMP connector to crash the service or exhaust its memory. This could lead to a complete disruption of message processing and communication between integrated business systems.

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

Quick answers

Is CVE-2026-49432 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-49432 being exploited in the wild.
How severe is CVE-2026-49432?
High severity, with a CVSS score of 7.5, published 30 June 2026.
Which products and versions are affected?
org.apache.activemq:activemq-all (Maven) < 5.19.8, ECOSYSTEM:introduced=0,fixed=5.19.8; org.apache.activemq:activemq-stomp (Maven) < 5.19.8, ECOSYSTEM:introduced=0,fixed=5.19.8; org.apache.activemq:apache-activemq (Maven) < 5.19.8, ECOSYSTEM:introduced=0,fixed=5.19.8.
Is there a fix for CVE-2026-49432?
Yes. org.apache.activemq:activemq-all (Maven): upgrade to 5.19.8 or later; org.apache.activemq:activemq-stomp (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-49432 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-49432?
Check whether you run org.apache.activemq:activemq-all (Maven), org.apache.activemq:activemq-stomp (Maven) or org.apache.activemq:apache-activemq (Maven) 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-stomp (Maven): upgrade to 5.19.8 or later
    # set org.apache.activemq:activemq-stomp 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

An improper input validation vulnerability exists in the STOMP protocol implementation of Apache ActiveMQ. A remote unauthenticated attacker can reach an exposed STOMP connector and trigger denial-of-service behavior by providing a negative 'content-length' value. In the NIO STOMP transport, this allows an attacker to stream body bytes that grow the per-connection command buffer beyond configured limits, resulting in an Out-of-Memory (OOM) crash. In the blocking STOMP protocol, the error triggers abnormal transport exception handling that forces connection closure. The issue is resolved in versions 6.2.7 and 5.19.8.

Affected products

  • Apache Software Foundation Apache ActiveMQ before 5.19.8, 6.0.0 to 6.2.7
  • Apache Software Foundation Apache ActiveMQ All before 5.19.8, 6.0.0 to 6.2.7
  • Apache Software Foundation Apache ActiveMQ Stomp before 5.19.8, 6.0.0 to 6.2.7

Identifiers

  • CVE-2026-49432
  • BIT-ACTIVEMQ-2026-49432
  • GHSA-xjwq-9jw5-jf7w

Timeline

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

References

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