RabbitMQ: Consecutive topic wildcards cause combinatorial routing work
CVE-2026-67419 is fixed in rabbitmq-server on 1 platform by DEBIAN-CVE-2026-67419 (version 4.3.6-1), released October 10, 2026. It is not reported as exploited. Patch Radar priority: Routine.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| rabbitmq-server · Debian 14 | 4.3.6-1 | DEBIAN-CVE-2026-67419 | Oct 10, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.