Quick answers
- Is CVE-2026-49270 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49270 being exploited in the wild.
- How severe is CVE-2026-49270?
- Medium severity, with a CVSS score of 5.9, published 1 June 2026.
- Which products and versions are affected?
- Apache Software Foundation ActiveMQ All 5.14.0 to 5.19.6, 6.0.0 to 6.2.5; org.apache.activemq:activemq-all (Maven) ECOSYSTEM:introduced=0,fixed=5.19.7; org.apache.activemq:activemq-broker (Maven) ECOSYSTEM:introduced=0,fixed=5.19.7; org.apache.activemq:apache-activemq (Maven) ECOSYSTEM:introduced=0,fixed=5.19.7.
- Is there a fix for CVE-2026-49270?
- Yes. org.apache.activemq:activemq-all (Maven): upgrade to 5.19.7 or later; org.apache.activemq:activemq-broker (Maven): upgrade to 5.19.7 or later; org.apache.activemq:apache-activemq (Maven): upgrade to 5.19.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49270 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-49270?
- 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.7 or later
# set org.apache.activemq:activemq-all to 5.19.7 in your pom.xml or build.gradle - org.apache.activemq:activemq-broker (Maven): upgrade to 5.19.7 or later
# set org.apache.activemq:activemq-broker to 5.19.7 in your pom.xml or build.gradle - org.apache.activemq:apache-activemq (Maven): upgrade to 5.19.7 or later
# set org.apache.activemq:apache-activemq to 5.19.7 in your pom.xml or build.gradle
Technical details
An information disclosure vulnerability (CWE-1230) exists in Apache ActiveMQ when brokers are configured with a network connector and 'syncDurableSubs' is set to true. The broker fails to enforce authentication before responding to 'BrokerInfo' commands via the OpenWire protocol. An unauthenticated remote attacker can exploit this to obtain a list of all durable topic subscriptions, including client identifiers, subscription names, topic destinations, and JMS selector expressions. The issue is resolved in versions 5.19.7 and 6.2.6.
Affected products
- Apache ActiveMQ Broker 5.14.0 to 5.19.6, 6.0.0 to 6.2.5
- Apache ActiveMQ All 5.14.0 to 5.19.6, 6.0.0 to 6.2.5
Identifiers
- CVE-2026-49270
- GHSA-hf52-78x8-6w3w
Timeline
- 2026-05-31: disclosed: Initial disclosure on oss-security mailing list
- 2026-06-01: advisory: GitHub and NVD advisories published