CVE-2026-67419

Published: Set 25, 2026 Last Modified: Set 25, 2026
ExploitDB:
Other exploit source:
Google Dorks:
HIGH 7,1
Attack Vector: network
Attack Complexity: low
Privileges Required: low
User Interaction: none
Confidentiality: N/A
Integrity: N/A
Availability: N/A

Description

AI Translation Available

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.

407

Inefficient Algorithmic Complexity

Incomplete
Common Consequences
Security Scopes Affected:
Availability
Potential Impacts:
Dos: Resource Consumption (Cpu) Dos: Resource Consumption (Memory) Dos: Resource Consumption (Other)
Applicable Platforms
All platforms may be affected
View CWE Details
1333

Inefficient Regular Expression Complexity

Draft
Common Consequences
Security Scopes Affected:
Availability
Potential Impacts:
Dos: Resource Consumption (Cpu)
Applicable Platforms
All platforms may be affected
View CWE Details
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-h964-v5mf-…
https://github.com/rabbitmq/rabbitmq-server/commit/c5ed7c4e97e02be688730803604c…
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.5
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-h964-v5mf-…