Bug 2541534 (CVE-2026-67419)

Summary:	CVE-2026-67419 rabbitmq-server: rabbitmq-server: Denial of Service via consecutive wildcards in topic binding keys
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security <prodsec-ir-bot>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	eglynn, jjoyce, jpretori, jschluet, lhh, mburns, mgarciac
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in RabbitMQ. An authenticated remote user with permissions to bind queues to a topic exchange and publish messages can cause a Denial of Service (DoS). By supplying consecutive wildcard characters within a topic binding key, the message routing engine redundantly evaluates matching states without caching results. This behavior causes severe CPU and memory exhaustion that can disrupt message routing across the entire 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:
Bug Depends On:	2547905
Bug Blocks:

Description OSIDB Bzimport 2026-09-25 16:59:11 UTC

RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive # segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. The matcher materializes duplicate destinations before deduplication, causing combinatorial CPU work and memory pressure that can disrupt routing for all tenants. This vulnerability is fixed in 4.3.5.