Advisory record · GHSA-hf52-78x8-6w3w

Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All have an Exposure of Sensitive Information Through Metadata vulnerability

CVSS 5.9 MediumEPSS 0.0037 · 30th percentile

Published by the GitHub Advisory Database at 1 Jun 2026, 09:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.activemq:apache-activemqMaven<5.19.7 || >=6.0.0, <6.2.65.19.7, 6.2.6
org.apache.activemq:activemq-brokerMaven<5.19.7 || >=6.0.0, <6.2.65.19.7, 6.2.6
org.apache.activemq:activemq-allMaven<5.19.7 || >=6.0.0, <6.2.65.19.7, 6.2.6
Identifiers
GHSA-hf52-78x8-6w3w · BIT-activemq-2026-49270 · CVE-2026-49270
Weakness (CWE)
CWE-1230
Published
1 Jun 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache ActiveMQ Broker, Apache ActiveMQ, and Apache ActiveMQ All are vulnerable before 5.19.7 and from 6.0.0 before 6.2.6. Brokers with a network connector that has syncDurableSubs set to true can be queried by an unauthenticated remote attacker, who can obtain a list of durable topic subscriptions, including client identifiers, subscription names, topic destinations, and JMS selector expressions. Upgrade to version 5.19.7 or 6.2.6.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.9 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0037, the 30th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.