CVE-2026-67219 json
RabbitMQ: Consistent-hash exchange unbounded weight
published 2026-09-23 46 d ago modified 2026-10-20 19 d ago also BIT-rabbitmq-2026-67219 , EUVD-2026-85654 , GHSA-m8pg-4x2h-jvgr
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- bitnami rabbitmq 3.13.15, 4.0.20, 4.1.11, 4.2.6
- vmware rabbitmq 3.13.15, 4.0.20, 4.1.11, 4.2.6
- pivotal_software rabbitmq 3.13.15, 4.0.20, 4.1.11, 4.2.6
- rabbitmq-server Debian 14 4.3.0-2
debian advisories DEBIAN-CVE-2026-67219
- rabbitmq-server4.3 hummingbird 1 4.3.6-1.hum1
red hat advisories RHSA-2026:67552
- rabbitmq-server Azure Linux 3.0 3.13.7-10
azure linux advisories AZL-105759
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-67219 updated cvss 6.5
rabbitmq: RabbitMQ: Denial of Service via unbounded consistent-hash exchange weight
-
Red Hat Hardened Images rabbitmq-server4.2 4.2.9-0.2.hum1affected: no fix planned “Will not fix”
-
Red Hat Hardened Images rabbitmq-server4.3 4.3.6-1.hum1fixed: vendor fix RHSA-2026:67552
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 45 d ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 4.0 | 6.0 | CVSS: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 |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | rabbitmq | >=3.13.0, <3.13.15 >=4.0.0, <4.0.20 >=4.1.0, <4.1.11 >=4.2.0, <4.2.6 |
3.13.15 4.0.20 4.1.11 4.2.6 |
Affected products
- rabbitmq rabbitmq-server
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
github.com
/rabbitmq/rabbitmq-server/security/advisories/GHSA-m8pg-4x2h-jvgr
vendor-advisory, advisory
-
github.com
/rabbitmq/rabbitmq-server/releases/tag/v4.2.6
release-notes, article
-
github.com
/rabbitmq/rabbitmq-server/releases/tag/v4.3.0
release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2026-67219
web
Sources
- CVE List CVE-2026-67219
- NVD CVE-2026-67219
- OSV BIT-rabbitmq-2026-67219
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.