{"id":29403,"date":"2026-09-26T04:31:44","date_gmt":"2026-09-25T20:31:44","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-61837"},"modified":"2026-09-26T04:31:44","modified_gmt":"2026-09-25T20:31:44","slug":"cve-2026-61837","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-61837","title":{"rendered":"CVE-2026-61837 &#8211; RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.3.3, 4.2.9, 4.1.14, and 4"},"content":{"rendered":"<p>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&#8217;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.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>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 <\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-29403","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/29403","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=29403"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=29403"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=29403"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}