{"id":"CVE-2026-61837","summary":"RabbitMQ: AMQP 1.0 management `GET /bindings` exposes full binding topology to any authenticated AMQP user without resource/management permission checks","details":"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.","aliases":["GHSA-w9hf-476r-443x"],"modified":"2026-09-27T03:47:29.301470515Z","published":"2026-09-25T16:22:43.927Z","database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/61xxx/CVE-2026-61837.json","unresolved_ranges":[{"source":"AFFECTED_FIELD","extracted_events":[{"introduced":"4.1.0"},{"fixed":"4.1.14"},{"introduced":"4.0.0"},{"fixed":"4.0.23"}]}],"cna_assigner":"GitHub_M","cwe_ids":["CWE-285","CWE-862"]},"references":[{"type":"WEB","url":"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9"},{"type":"WEB","url":"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/61xxx/CVE-2026-61837.json"},{"type":"ADVISORY","url":"https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-w9hf-476r-443x"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-61837"},{"type":"FIX","url":"https://github.com/rabbitmq/rabbitmq-server/commit/341e3f2795ebd1f816e712530f651a3221d23ad9"},{"type":"FIX","url":"https://github.com/rabbitmq/rabbitmq-server/commit/b94004dea530f961b3dc649d94969b89f1a3183f"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://github.com/rabbitmq/rabbitmq-server","events":[{"introduced":"1929eeadf9b2bac12c5434fb56884ef27370580e"},{"introduced":"95c501fbad76c66156346cf364d158d6e30aa4d9"},{"fixed":"1d284b2d2a1e2f845ad22b0d5ee38ec372d50802"},{"fixed":"47d6d6457c7d1a440daed643cb7d76bba313e79c"},{"fixed":"341e3f2795ebd1f816e712530f651a3221d23ad9"},{"fixed":"b94004dea530f961b3dc649d94969b89f1a3183f"}],"database_specific":{"extracted_events":[{"introduced":"4.3.0"},{"fixed":"4.3.3"},{"introduced":"4.2.0"},{"fixed":"4.2.9"}],"source":["AFFECTED_FIELD","REFERENCES"]}}],"versions":["v4.2.8","v4.3.2","v4.2.7","v4.3.1","v4.2.6","v4.3.0","v4.2.5","v4.2.4","v4.2.3","v4.2.2","v4.2.1","v4.2.0"],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-61837.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V4","score":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N"}]}