CVE-2026-66076 json
RabbitMQ: Cross-vhost quorum-queue status and stream tracking disclosure
published 2026-09-23 46 d ago modified 2026-10-20 19 d ago also BIT-rabbitmq-2026-66076 , EUVD-2026-85623 , GHSA-j45q-v7g2-82ph
- 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 26%
- 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, is_authorized/2 calls rabbit_mgmt_util:is_authorized/2, which checks only the management tag, instead of is_authorized_vhost/2. The /api/queues/quorum/:vhost/:queue/status handler reads the vhost from the path without checking that the user can access it. Any management-tagged user can therefore read Raft status, including leader, members, term, and commit index, for quorum queues in inaccessible vhosts, exposing cross-tenant queue names and cluster topology. The management plugin must be enabled and the attacker must have a management tag. 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-66076
- 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-11
azure linux advisories AZL-109722
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-66076 updated cvss 4.3
rabbitmq: RabbitMQ: Information disclosure via cross-vhost authorization bypass
-
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
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 45 d ago
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-j45q-v7g2-82ph referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 2.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N |
| CNA | 4.0 | 2.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/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:H/I:N/A:N |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
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-862 Missing Authorization
References
-
github.com
/rabbitmq/rabbitmq-server/security/advisories/GHSA-j45q-v7g2-82ph
exploit, vendor-advisory, advisory
-
github.com
/rabbitmq/rabbitmq-server/releases/tag/v4.2.6
release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2026-66076
web
Sources
- CVE List CVE-2026-66076
- NVD CVE-2026-66076
- OSV BIT-rabbitmq-2026-66076
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.