RabbitMQ: Cross-vhost quorum-queue status and stream tracking disclosure
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-66076
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 10:00 UTC · Revision 1
Source evidence
RabbitMQ: Cross-vhost quorum-queue status and stream tracking disclosure
core-osv · Original sourcePublished 23 Sept 2026, 19:57 UTC
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.
osv:CVE-2026-66076
Complete source record
{
"id": "fcb0c71d537169aad563ac16f02eadc1b102df8359566376e238b2d2a0635a07",
"url": "https://osv.dev/vulnerability/CVE-2026-66076",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "RabbitMQ: Cross-vhost quorum-queue status and stream tracking disclosure",
"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.",
"evidence": "osv:CVE-2026-66076",
"products": [],
"severity": "low",
"structured": {
"id": "CVE-2026-66076",
"aliases": [
"BIT-rabbitmq-2026-66076",
"CVE-2026-66076",
"GHSA-j45q-v7g2-82ph"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/rabbitmq/rabbitmq-server",
"type": "GIT",
"events": [
{
"introduced": "95c501fbad76c66156346cf364d158d6e30aa4d9"
},
{
"fixed": "8a56c37f099a7bf609a555de3f0ff8ed23964d20"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "4.2.0"
},
{
"fixed": "4.2.6"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "8a56c37f099a7bf609a555de3f0ff8ed23964d20"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v4.2.6"
},
{
"cpe": "cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "4.2.0"
},
{
"fixed": "4.2.6"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"v4.2.5",
"v4.2.4",
"v4.2.3",
"v4.2.2",
"v4.2.1",
"v4.2.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-66076.json"
}
}
],
"modified": "2026-10-28T02:30:50.217563627Z",
"provider": "osv",
"references": [
"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/66xxx/CVE-2026-66076.json",
"https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-j45q-v7g2-82ph",
"https://nvd.nist.gov/vuln/detail/CVE-2026-66076"
],
"provider_metadata": {
"cwe_ids": [
"CWE-862"
],
"cna_assigner": "GitHub_M",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"introduced": "3.13.0"
},
{
"fixed": "3.13.15"
},
{
"introduced": "4.0.0"
},
{
"fixed": "4.0.20"
},
{
"introduced": "4.1.0"
},
{
"fixed": "4.1.11"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
}
]
}
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/66xxx/CVE-2026-66076.json"
}
},
"related_cves": [
{
"value": "CVE-2026-66076",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 518949,
"published_at": "2026-09-23T19:57:11.906+00:00"
}