Quick answers
- Is CVE-2026-67419 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67419 being exploited in the wild.
- How severe is CVE-2026-67419?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- RabbitMQ before 4.3.5.
- Is there a fix for CVE-2026-67419?
- A patch was published on 2026-08-17: RabbitMQ 4.3.5 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-67419 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-67419?
- Check whether you run RabbitMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authenticated user with permission to bind queues to topic exchanges can use consecutive # (multi-segment) wildcards in binding keys to force the router's trie-node matcher to revisit states without memoization, creating combinatorial computational work. The matcher materializes duplicate destinations before deduplication, leading to memory pressure and routing disruption. The fix limits multi-segment wildcard matchers to two per binding key.
Affected products
- RabbitMQ RabbitMQ before 4.3.5
Timeline
- 2026-09-25: disclosed
- 2026-08-17: patched: RabbitMQ 4.3.5 released