CVE-2026-67413

published 25 Sep 2026 · updated 17 Oct 2026

RabbitMQ: Authenticated RabbitMQ JMS Topic Selector Users Can Consume Broker CPU with an Unbounded LIKE Regular Expression

6.0MediumCVSS 6.0EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.

RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.23, 4.1.14, 4.2.9, and 4.3.3, the optional rabbitmq_jms_topic_exchange plugin's x-jms-topic exchange accepted a client-controlled rjms_erlang_selector binding expression whose LIKE evaluator expanded percent and underscore wildcards into overlapping PCRE fragments. It executed those fragments with raw re:run/3 without match or recursion limits, allowing an authenticated tenant that can bind and publish to consume broker scheduler CPU and deny service with pathological selectors. This issue is fixed in versions 4.0.23, 4.1.14, 4.2.9, and 4.3.3.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
rabbitmq>=4.0.0 <4.0.23, >=4.1.0 <4.1.14, >=4.2.0 <4.2.9, >=4.3.0 <4.3.3

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-67413 severity on Zeptric[![CVE-2026-67413](https://zeptric.io/badge/cve/CVE-2026-67413.svg)](https://zeptric.io/cve/CVE-2026-67413)