Quick answers
- Is CVE-2026-67413 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67413 being exploited in the wild.
- How severe is CVE-2026-67413?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- VMware RabbitMQ 4.0.0 to 4.0.22, 4.1.0 to 4.1.13, 4.2.0 to 4.2.8, 4.3.0 to 4.3.2.
- Is there a fix for CVE-2026-67413?
- A patch was published on 2026: Fixed in versions 4.0.23, 4.1.14, 4.2.9, and 4.3.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-67413 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-67413?
- Check whether you run VMware 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
The rabbitmq_jms_topic_exchange plugin's x-jms-topic exchange accepts client-controlled rjms_erlang_selector binding expressions in which LIKE wildcard evaluators (% and _) are expanded into overlapping PCRE fragments executed via raw re:run/3 without match or recursion limits. An authenticated tenant with bind and publish permissions can trigger pathological regex matching causing broker scheduler CPU exhaustion and denial of service.
Affected products
- VMware RabbitMQ 4.0.0 to 4.0.22, 4.1.0 to 4.1.13, 4.2.0 to 4.2.8, 4.3.0 to 4.3.2
Timeline
- 2026-09-25: disclosed
- 2026: patched: Fixed in versions 4.0.23, 4.1.14, 4.2.9, and 4.3.3