What’s Vulnerable › Vulnerabilities

CVE-2026-61837: RabbitMQ: AMQP 1.0 management `GET /bindings` exposes full binding topology to any authenticated AMQP user without resource/management permission checks

• Severity: medium (CVSS 5.3 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.3% probability of exploitation in the next 30 days
• Public exploit or detection template: yes
• Published: 2026-09-25 · updated 2026-10-15
• Weakness: CWE-285

Description

RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.3.3, 4.2.9, 4.1.14, and 4.0.23, AMQP 1.0 management GET /bindings exposes full binding topology to any authenticated AMQP user without resource/management permission checks. the AMQP 1.0 HTTP-over-AMQP management endpoint GET /bindings (the rabbitamqpmanagement handler) enumerates bindings between an arbitrary source exchange and destination queue/exchange in the caller's virtual host without performing any resource-level permission check. Unlike every sibling operation in the same module (which call checkresourceaccess / bindingchecks), the GET handler ignores the authenticated User and returns the binding list unchanged. As a result, any authenticated AMQP 1.0 client that can open a management link pair , including users with no management/monitoring/policymaker/administrator tag , can enumerate the complete binding topology (source exchanges, destination queues/exchanges, routing keys, and binding arguments) of the virtual host they can access. The equivalent HTTP management API (GET /api/bindings) Confidentiality impact: a non-management AMQP 1.0 user can enumerate the complete routing topology of any virtual host it can connect to , every (source exchange, destination queue/exchange, routing key, binding arguments) This issue is fixed in versions 4.3.3, 4.2.9, 4.1.14, and 4.0.23.

Affected products

• rabbitmq-server: from 4.0.0 before 4.0.23; from 4.1.0 before 4.1.14; from 4.2.0 before 4.2.9; from 4.3.0 before 4.3.3 — fixed in 4.0.23, 4.1.14, 4.2.9, 4.3.3

How to fix

Upgrade to a fixed version: rabbitmq-server 4.0.23, 4.1.14, 4.2.9, 4.3.3. Check the vendor advisory for mitigations.

References

• https://github.com/rabbitmq/rabbitmq-server/commit/341e3f2795ebd1f816e712530f651a3221d23ad9
• https://github.com/rabbitmq/rabbitmq-server/commit/b94004dea530f961b3dc649d94969b89f1a3183f
• https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9
• https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3
• https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-w9hf-476r-443x
• https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-w9hf-476r-443x

Get alerted when CVE-2026-61837 or the next vulnerability affects your stack