CVE-2026-54475: Apache ActiveMQ missing authorization in temporary destinations

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

Apache ActiveMQ is a popular open-source message broker used to facilitate communication between different software applications. A security flaw in how the system handles 'temporary destinations' allows unauthorized users to intercept or consume messages intended for other connections. This could lead to the exposure of sensitive data being transmitted through the message broker.

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

Quick answers

Is CVE-2026-54475 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-54475 being exploited in the wild.
How severe is CVE-2026-54475?
High severity, with a CVSS score of 7.5, published 30 June 2026.
Which products and versions are affected?
Apache Software Foundation ActiveMQ All before 5.19.8, 6.0.0 before 6.2.7; org.apache.activemq:activemq-all (Maven) < 5.19.8, ECOSYSTEM:introduced=0,fixed=5.19.8; org.apache.activemq:activemq-broker (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-54475?
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-54475 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-54475?
Check whether you run Apache Software Foundation ActiveMQ All, 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 missing authorization vulnerability exists in Apache ActiveMQ Classic where temporary destinations are not properly isolated to the connection that created them. The root cause is that isolation checks are performed only on the client side rather than being enforced by the broker. An attacker with a valid connection to the broker can exploit this to consume messages from a temporary destination belonging to a different connection. This affects ActiveMQ Broker, ActiveMQ All, and ActiveMQ versions prior to 5.19.8 and 6.x versions prior to 6.2.7. Users should upgrade to version 6.2.7 to resolve this issue.

Affected products

  • Apache Software Foundation ActiveMQ Broker before 5.19.8, 6.0.0 before 6.2.7
  • Apache Software Foundation ActiveMQ All before 5.19.8, 6.0.0 before 6.2.7
  • Apache Software Foundation ActiveMQ before 5.19.8, 6.0.0 before 6.2.7

Identifiers

  • CVE-2026-54475
  • BIT-ACTIVEMQ-2026-54475
  • GHSA-mhp6-f224-j2c3

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.