Описание
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.
A flaw was found in RabbitMQ. An authenticated remote user with permissions to bind queues to a topic exchange and publish messages can cause a Denial of Service (DoS). By supplying consecutive wildcard characters within a topic binding key, the message routing engine redundantly evaluates matching states without caching results. This behavior causes severe CPU and memory exhaustion that can disrupt message routing across the entire broker.
Отчет
This flaw is rated as Moderate severity because exploitation requires an authenticated client with permissions to declare queue bindings on a topic exchange and publish messages through it. In typical Red Hat environments such as Red Hat OpenStack Platform, RabbitMQ operates on internal networks with tightly managed service credentials, limiting the pool of potential attackers to trusted accounts. However, an authorized tenant or compromised credential could craft binding keys containing consecutive multi-segment wildcard tokens (#), causing the broker to perform exponential pattern-matching work during message routing. The resulting CPU exhaustion degrades or halts message delivery for all tenants sharing the affected broker instance.
Меры по смягчению последствий
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Hardened Images | rabbitmq-server4.2 | Will not fix | ||
| Red Hat OpenStack Platform 13 (Queens) | rabbitmq-server | Out of support scope | ||
| Red Hat OpenStack Platform 16.2 | rabbitmq-server | Out of support scope | ||
| Red Hat OpenStack Platform 17.1 | rabbitmq-server | Out of support scope | ||
| Red Hat OpenStack Platform 18.0 | rabbitmq-server | Fix deferred | ||
| Red Hat Hardened Images | rabbitmq-server4-3-main-4.3.6-1.hum1 | Fixed | RHSA-2026:67552 | 15.09.2026 |
Показывать по
Ссылки на источники
Дополнительная информация
Статус:
EPSS
6.5 Medium
CVSS3
Связанные уязвимости
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.
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.
RabbitMQ: Consecutive topic wildcards cause combinatorial routing work
RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authe ...
EPSS
6.5 Medium
CVSS3