# CVE-2026-61837: RabbitMQ AMQP 1.0 management binding enumeration

Source: https://junglewise.ai/threats/cve-2026-61837-rabbitmq-is-a-messaging-and-streaming-broker-from-4-0-0-until-4-3  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-25. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-61837 · Severity: info · Published 2026-09-25

RabbitMQ is a message broker that routes messages between applications. The AMQP 1.0 management interface allows any authenticated user to enumerate the complete routing topology (exchanges, queues, and routing rules) of their virtual host, even if they lack management permissions. This exposes sensitive infrastructure details that should be restricted to administrators.

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

## Quick answers

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

**How severe is CVE-2026-61837?** Informational severity, published 25 September 2026.

**Which products and versions are affected?** RabbitMQ 4.0.0 to 4.0.22, 4.1.0 to 4.1.13, 4.2.0 to 4.2.8, 4.3.0 to 4.3.2.

**Is there a fix for CVE-2026-61837?** A patch was published on 2026: Fixed in versions 4.3.3, 4.2.9, 4.1.14, and 4.0.23 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

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

**Am I affected by CVE-2026-61837?** 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 GET /bindings endpoint in the AMQP 1.0 management module (rabbitamqpmanagement handler) fails to perform resource-level permission checks, unlike sibling operations. Authenticated AMQP 1.0 clients without management tags can invoke this endpoint to retrieve full binding topology including source exchanges, destination queues, routing keys, and binding arguments. The fix adds resource access validation aligned with other binding handlers.

## Affected products

- RabbitMQ RabbitMQ 4.0.0 to 4.0.22, 4.1.0 to 4.1.13, 4.2.0 to 4.2.8, 4.3.0 to 4.3.2

## Timeline

- 2026-09-25: disclosed: CVE-2026-61837 published
- 2026: patched: Fixed in versions 4.3.3, 4.2.9, 4.1.14, and 4.0.23

## References

- [https://github.com/rabbitmq/rabbitmq-server/commit/341e3f2795ebd1f816e712530f651a3221d23ad9](https://github.com/rabbitmq/rabbitmq-server/commit/341e3f2795ebd1f816e712530f651a3221d23ad9)
- [https://github.com/rabbitmq/rabbitmq-server/commit/b94004dea530f961b3dc649d94969b89f1a3183f](https://github.com/rabbitmq/rabbitmq-server/commit/b94004dea530f961b3dc649d94969b89f1a3183f)

## 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)