# CVE-2026-66076: RabbitMQ missing authorization in quorum queue status endpoint

Source: https://junglewise.ai/threats/cve-2026-66076-rabbitmq-is-a-messaging-and-streaming-broker-prior-to-versions-3  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-23. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-66076 · Severity: info · Published 2026-09-23

RabbitMQ is a messaging and streaming broker used by organizations to handle mission-critical message delivery. A vulnerability in the management API allows any user with a management tag to view the Raft status (leader information, cluster members, and topology) of quorum queues in virtual hosts they should not have access to. This could leak cross-tenant queue names and expose cluster topology details that could be used to plan further attacks.

Technologies: [RabbitMQ](https://junglewise.ai/threats/technologies/rabbitmq-rabbitmq). Vendors: [RabbitMQ](https://junglewise.ai/threats/vendors/rabbitmq).

## Quick answers

**Is CVE-2026-66076 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-66076 being exploited in the wild.

**How severe is CVE-2026-66076?** Informational severity, published 23 September 2026.

**Which products and versions are affected?** RabbitMQ 3.13.0 to 3.13.14, 4.0.0 to 4.0.19, 4.1.0 to 4.1.10, 4.2.0 to 4.2.5.

**Is there a fix for CVE-2026-66076?** A patch was published on 2026-09-23: Fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-66076 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-66076?** Check whether you run RabbitMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a missing authorization check (IDOR) in the /api/queues/quorum/:vhost/:queue/status endpoint handler. It calls is_authorized/2 which performs only a tag check rather than the required is_authorized_vhost/2 check. An attacker with a management tag can extract sensitive cluster topology and queue information from inaccessible vhosts. The management plugin must be enabled and the attacker must possess a management tag.

## Affected products

- RabbitMQ RabbitMQ 3.13.0 to 3.13.14, 4.0.0 to 4.0.19, 4.1.0 to 4.1.10, 4.2.0 to 4.2.5

## Timeline

- 2026-09-23: disclosed
- 2026-09-23: patched: Fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0

## References

- [https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6](https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6)
- [https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-j45q-v7g2-82ph](https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-j45q-v7g2-82ph)

## Related threats

- [RabbitMQ OAuth privilege escalation via stale token tags](https://junglewise.ai/threats/cve-2026-67420-rabbitmq-is-a-messaging-and-streaming-broker-from-3-13-0-until-3)
- [RabbitMQ topic exchange denial of service via duplicate matchers](https://junglewise.ai/threats/cve-2026-67419-rabbitmq-is-a-messaging-and-streaming-broker-prior-to-4-3-5-an)
- [RabbitMQ Shovel denial of service via atom exhaustion](https://junglewise.ai/threats/cve-2026-67415-rabbitmq-is-a-messaging-and-streaming-broker-from-4-2-0-until-4-2)
- [RabbitMQ MQTT loopback user bypass via PROXY Protocol](https://junglewise.ai/threats/cve-2026-67411-rabbitmq-is-a-messaging-and-streaming-broker-from-3-13-0-until-3)
- [RabbitMQ OAuth2 client secret exposure via unauthenticated endpoint](https://junglewise.ai/threats/cve-2026-67410-rabbitmq-is-a-messaging-and-streaming-broker-from-4-2-0-until-4-3)