|
|
Message-ID: <9f1296ff-7fcd-d2d2-72e5-4e7ef2bad1c4@apache.org> Date: Sun, 31 May 2026 16:18:07 +0000 From: "Christopher L. Shannon" <cshannon@...che.org> To: oss-security@...ts.openwall.com Subject: CVE-2026-49270: Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All: Durable Subscription Disclosure via Crafted BrokerInfo (OpenWire) Severity: moderate Affected versions: - Apache ActiveMQ Broker (org.apache.activemq:activemq-broker) 5.14.0 before 5.19.7 - Apache ActiveMQ Broker (org.apache.activemq:activemq-broker) 6.0.0 before 6.2.6 - Apache ActiveMQ (org.apache.activemq:activemq-all) 5.14.0 before 5.19.7 - Apache ActiveMQ (org.apache.activemq:activemq-all) 6.0.0 before 6.2.6 - Apache ActiveMQ All (org.apache.activemq:apache-activemq) 5.14.0 before 5.19.7 - Apache ActiveMQ All (org.apache.activemq:apache-activemq) 6.0.0 before 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. Credit: Basel Khaled (finder) References: https://activemq.apache.org/ https://www.cve.org/CVERecord?id=CVE-2026-49270
Powered by blists - more mailing lists
Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.