Vulnerability Description
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.
Related Weaknesses (CWE)
References
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-j45q-v7g2-8
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-j45q-v7g2-8
FAQ
What is CVE-2026-66076?
CVE-2026-66076 is a documented vulnerability. 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,...
How severe is CVE-2026-66076?
CVSS scoring is not yet available for CVE-2026-66076. Check NVD for updates.
Is there a patch for CVE-2026-66076?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.