# CVE-2026-67413: RabbitMQ JMS topic exchange denial of service via regex wildcard expansion

Source: https://junglewise.ai/threats/cve-2026-67413-rabbitmq-is-a-messaging-and-streaming-broker-from-4-0-0-until-4-0  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-25. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-67413 · Severity: info · Published 2026-09-25

RabbitMQ is a message broker that routes messages between applications. The optional JMS topic exchange plugin allows authenticated users to bind queues using expressions called selectors. An authenticated user can craft a malicious selector with wildcard patterns that, when evaluated, causes the broker to consume excessive CPU and become unresponsive, disrupting message delivery for all users.

Technologies: [VMware RabbitMQ](https://junglewise.ai/threats/technologies/vmware-rabbitmq). Vendors: [VMware](https://junglewise.ai/threats/vendors/vmware).

## 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

## References

- [https://github.com/rabbitmq/rabbitmq-server/commit/20203c50ea6ff459d462b2d4355326d3a870682c](https://github.com/rabbitmq/rabbitmq-server/commit/20203c50ea6ff459d462b2d4355326d3a870682c)
- [https://github.com/rabbitmq/rabbitmq-server/commit/60de2fbbcd812ab294985cef260cc2f1b1a02a5b](https://github.com/rabbitmq/rabbitmq-server/commit/60de2fbbcd812ab294985cef260cc2f1b1a02a5b)

## Related threats

- [RabbitMQ MQTT 5 parser invalid property denial of service](https://junglewise.ai/threats/cve-2026-67418-rabbitmq-is-a-messaging-and-streaming-broker-from-3-13-0-until-3)
- [RabbitMQ AMQP 1.0 parser descriptor validation bypass](https://junglewise.ai/threats/cve-2026-67416-rabbitmq-is-a-messaging-and-streaming-broker-from-4-0-0-until-4-0)
- [RabbitMQ AMQP 1.0 parser memory exhaustion](https://junglewise.ai/threats/cve-2026-67414-rabbitmq-is-a-messaging-and-streaming-broker-from-4-0-0-until-4-0)
- [RabbitMQ Management XSS via queue name in OAuth UI](https://junglewise.ai/threats/cve-2026-67421-rabbitmq-is-a-messaging-and-streaming-broker-from-3-13-0-until-3)
- [RabbitMQ Federation upstream authorization bypass](https://junglewise.ai/threats/cve-2026-67412-rabbitmq-is-a-messaging-and-streaming-broker-from-3-13-0-until-4)