Vulnerability Description
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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Broadcom | Rabbitmq Server | >= 4.3.0, < 4.3.5 |
Related Weaknesses (CWE)
References
- https://github.com/rabbitmq/rabbitmq-server/commit/c5ed7c4e97e02be688730803604ccPatch
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.5Release Notes
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-h964-v5mf-2Vendor AdvisoryExploitMitigation
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-h964-v5mf-2Vendor AdvisoryExploitMitigation
FAQ
What is CVE-2026-67419?
CVE-2026-67419 is a vulnerability with a CVSS score of 6.5 (MEDIUM). 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 b...
How severe is CVE-2026-67419?
CVE-2026-67419 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-67419?
Check the references section above for vendor advisories and patch information. Affected products include: Broadcom Rabbitmq Server.