All vulnerabilities

Servers and applications

CVE-2026-61837

AMQP 1.0 management `GET /bindings` exposes full binding topology to any authenticated AMQP user without resource/management permission checks

Severity
Medium 6.3
Published
23 Jul 2026
Last changed
15 Oct 2026
Added to UpHeron
1 Nov 2026
Fixed in
4.0.23, 4.1.14, 4.2.9, 4.3.3
Exploit chance
0.3% in the next 30 daysHigher than 22% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Improper authorization (CWE-285)Missing authorization (CWE-862)
Attack
Over the network · Needs a user account · No user action needed
CVSS 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Also known as
GHSA-w9hf-476r-443x
Sources
NVD, Project advisories (GitHub)

Description

The AMQP 1.0 HTTP-over-AMQP management endpoint GET /bindings (the rabbit_amqp_management 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 check_resource_access / binding_checks), 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) requires a management-tagged user; the AMQP 1.0 path does not, so this crosses a documented confidentiality boundary.

From rabbitmq/rabbitmq-server's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
RabbitMQServers and applications · cpe:a:broadcom: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
RabbitMQServers and applications · github:rabbitmq/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

About RabbitMQ

open source message broker, sometimes referred to as "Rabbit"

From Wikidata, CC0 1.0.
Docker Hub pulls
3,918,841,187Docker Hub, 15 Nov 2026
GitHub stars
13,973GitHub, 15 Nov 2026
Forks
4,032GitHub, 15 Nov 2026
Latest release
v4.4.0GitHub, 15 Nov 2026
Released
19 Oct 2026GitHub
Developer
Jean-Sébastien PédronWikidata
License
Mozilla Public License, version 2.0Wikidata
Written in
ErlangWikidata
First published on GitHub
20 Sept 2010GitHub

Release lines

ReleaseLatestSecurity fixes
4.44.4.0Until 31 Jul 2027
4.34.3.7Until 31 Jan 2027
4.24.2.9Ended 31 Jul 2026
4.14.1.8Ended 30 Jan 2026
4.04.0.9Ended 30 Apr 2025
3.133.13.7Ended 30 Sept 2024

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-61837
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-61837
  • GitHub Advisory Database https://github.com/advisories/GHSA-w9hf-476r-443x
  • github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-w9hf-476r-443x