CVE-2026-66076

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. Limited direct impact.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-09-23 20:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-19 20:36 UTC Last updatedMost recent change to the record

Details

Published

2026-09-23 20:17 UTC

Last modified

2026-10-19 20:36 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-862 · Missing authorization

Record status

Analyzed

Affected

• Broadcom Rabbitmq Server < 3.13.15
• Broadcom Rabbitmq Server < 4.0.20
• Broadcom Rabbitmq Server < 4.1.11
• Broadcom Rabbitmq Server < 4.2.6

Attack profile CVSS 4.0 · 2.3

Attack vector

Network

Complexity

Low

Attack requirements

Present

Privileges needed

Low

User interaction

None

Confidentiality

Low

Integrity

None

Availability

None