CVE-2026-67219
published 2026-09-23CVE-2026-67219: RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, add_binding/3 parses the routing key as an integer…
PriorityP337medium6.5CVSS 3.1
AVNACLPRLUINSUCNINAH
EPSS
0.30%
21.7th percentile
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, add_binding/3 parses the routing key as an integer weight N and computes ring positions with lists:seq(NextN0, NextN0 + N - 1). validate_binding/2 only checks N >= 1 , no upper bound. The resulting list is stored in the exchange's Khepri record, replicated cluster-wide, and reloaded on restart. A user with write permission on a consistent-hash exchange and read on a queue can create a binding whose routing key (the hash-ring weight) is an arbitrarily large integer. The broker allocates a list of that many integers via lists:seq/2 and persists it to Khepri across all cluster nodes , a single binding with weight 100000000 allocates ~800 MB on every node and survives restarts. Preconditions include rabbitmq_consistent_hash_exchange plugin enabled write permission on a consistent-hash exchange + read on a queue (standard binding perms). This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| broadcom | rabbitmq_server | >= 3.13.0 < 3.13.15 | 3.13.15 |
| broadcom | rabbitmq_server | >= 4.0.0 < 4.0.20 | 4.0.20 |
| broadcom | rabbitmq_server | >= 4.1.0 < 4.1.11 | 4.1.11 |
| broadcom | rabbitmq_server | >= 4.2.0 < 4.2.6 | 4.2.6 |
| rabbitmq | rabbitmq-server | — | — |
| rabbitmq | rabbitmq-server | — | — |
| rabbitmq | rabbitmq-server | — | — |
| rabbitmq | rabbitmq-server | — | — |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvdv4.06.0MEDIUMCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
vendor_redhat6.0MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
RabbitMQ up to 3.13.14/4.0.19/4.1.10/4.2.5 Consistent Hash Exchange add_binding allocation of resources
vuldb·2026-09-23·CVSS 6.0
CVE-2026-67219 [MEDIUM] RabbitMQ up to 3.13.14/4.0.19/4.1.10/4.2.5 Consistent Hash Exchange add_binding allocation of resources
A vulnerability labeled as problematic has been found in RabbitMQ up to 3.13.14/4.0.19/4.1.10/4.2.5. This affects the function add_binding of the component Consistent Hash Exchange. The manipulation results in allocation of resources.
This vulnerability is known as CVE-2026-67219. It is possible to launch the attack remotely. No exploit is available.
The affected component should be upgraded.
Red Hat
rabbitmq: RabbitMQ: Denial of Service via unbounded consistent-hash exchange weight
vendor_redhat·2026-09-23·CVSS 6.0
CVE-2026-67219 [MEDIUM] CWE-606 rabbitmq: RabbitMQ: Denial of Service via unbounded consistent-hash exchange weight
rabbitmq: RabbitMQ: Denial of Service via unbounded consistent-hash exchange weight
A flaw was found in RabbitMQ. A user with write permission on a consistent-hash exchange and read on a queue can create a binding with an arbitrarily large integer as its routing key, which acts as a hash-ring weight. This unbounded weight causes the broker to allocate a significant amount of memory, potentially leading to a Denial of Service (DoS) across all cluster nodes in the cluster.
Package: rabbitmq-server4.2 (Red Hat Hardened Images) - Will not fix
Package: rabbitmq-server4.3 (Red Hat Hardened Images) - Affected
No detection rules found.
No public exploits indexed.
2026-09-23
Published