Bug 2566821 (CVE-2026-108949)

Summary:	CVE-2026-108949 org.apache.activemq/activemq-broker: activemq-broker: Denial of Service via memory leak from rejected subscriptions
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security DevOps Team <prodsec-dev>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	gmalinko, janstey, pdelbell, rhel-process-autobot, rstepani, watson-tool-maintainers
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in Apache ActiveMQ. When an authenticated client requests access to a temporary destination owned by another connection, the broker rejects the request but fails to remove the rejected subscription entry from internal memory. By repeatedly issuing these requests, an authenticated attacker can cause an unbounded memory leak, ultimately leading to an Out-of-Memory (OOM) condition and a Denial of Service (DoS) for the broker.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-11-04 10:28:39 UTC

Denial of Service via OOM vulnerability in Apache ActiveMQ, ActiveMQ Broker.



An authenticated OpenWire client that sends a ConsumerInfo for a temporary queue/topic owned by another connection is rejected with InvalidDestinationException, but the rejected Subscription is left behind in the region's subscriptions map. Repeating the request leaks broker heap until OOM because the broker does not clean up the rejected subscriptions in the map.



This issue affects Apache ActiveMQ: from 6.0.0 before 6.3.3, before 5.19.12; ActiveMQ Broker: from 6.0.0 before 6.3.3, before 5.19.12.



Users are recommended to upgrade to version 6.4.0, 6.3.3, or 5.19.12, which fixes the issue.