{"schema":"threatline.record/2","record":{"id":"CVE-2026-61837","aliases":["GHSA-w9hf-476r-443x"],"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.","categories":["Unclassified"],"product":"rabbitmq-server","vendor":"rabbitmq","ecosystem":null,"affected_ranges":[{"source":"CVE List","source_url":"https://www.cve.org/CVERecord?id=CVE-2026-61837","source_modified_at":"2026-09-29T19:27:59.221Z","fetched_at":"2026-10-23T18:52:38.922436Z","product":"rabbitmq-server","vendor":"rabbitmq","versions":[{"version":">= 4.3.0, < 4.3.3","status":"affected"},{"version":">= 4.2.0, < 4.2.9","status":"affected"},{"version":">= 4.1.0, < 4.1.14","status":"affected"},{"version":">= 4.0.0, < 4.0.23","status":"affected"}],"defaultStatus":null}],"fixed_versions":[],"cvss":6.3,"severity":"Medium","kev":{"listed":false},"epss":{"probability":0.00256,"percentile":0.16309,"score_date":"2026-10-23"},"published_at":"2026-09-25T16:22:43.927Z","modified_at":"2026-09-29T19:27:59.221Z","provenance":[{"source":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-61837","fetched_at":"2026-10-23T18:52:38.922436Z","source_modified_at":"2026-09-29T19:27:59.221Z"},{"source":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-61837","fetched_at":"2026-10-23T18:42:43.628194Z","source_modified_at":"2026-10-23"}],"sources":["CVE List","EPSS"],"references":[{"source":"CVE List","url":"https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-w9hf-476r-443x","tags":["exploit"]},{"source":"CVE List","url":"https://github.com/rabbitmq/rabbitmq-server/commit/341e3f2795ebd1f816e712530f651a3221d23ad9","tags":["x_refsource_MISC"]},{"source":"CVE List","url":"https://github.com/rabbitmq/rabbitmq-server/commit/b94004dea530f961b3dc649d94969b89f1a3183f","tags":["x_refsource_MISC"]},{"source":"CVE List","url":"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9","tags":["x_refsource_MISC"]},{"source":"CVE List","url":"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3","tags":["x_refsource_MISC"]}],"locations":[],"motoko_assessment":{"status":"requires_architecture_review","automatic_remediation":false},"cve_state":"PUBLISHED","cvss_source":"CVE List","ssvc":{"exploitation":"poc","automatable":"no","technical_impact":"partial","assessed_at":"2026-09-29T19:27:34.351868Z"},"classification":{"method":"product-first software-layer rules","rules_version":"2.1","matched_on":null,"confidence":"unknown","reviewed":false},"change_timestamp":"2026-09-29T19:27:59.221Z","content_hash":"d8a5e84bbc2bc18a074bf30e1ce00a9135e2f8b7efb9291f8ebbe4fb1e18596e"}}