Skip to content
Fencer Vulns
medium 5.3

CVE-2026-61837 json

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

published 2026-09-25 44 d ago modified 2026-10-16 24 d ago also BIT-rabbitmq-2026-61837 , EUVD-2026-87227 , GHSA-w9hf-476r-443x

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 22%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami rabbitmq 4.0.23, 4.1.14, 4.2.9, 4.3.3
  • pivotal_software rabbitmq 4.0.23, 4.1.14, 4.2.9, 4.3.3
  • vmware rabbitmq 4.0.23, 4.1.14, 4.2.9, 4.3.3
  • rabbitmq-server Debian 14 4.3.6-1

debian advisories DEBIAN-CVE-2026-61837

  • rabbitmq-server4.3 hummingbird 1 4.3.6-1.hum1

red hat advisories RHSA-2026:67552

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-61837 updated cvss 4.3

rabbitmq-server: RabbitMQ: Information disclosure via improper access control in AMQP management endpoint

  • Red Hat Hardened Images rabbitmq-server4.2 4.2.9-0.2.hum1
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 13 (Queens) rabbitmq-server Red Hat OpenStack Platform 16.2 rabbitmq-server Red Hat OpenStack Platform 17.1 rabbitmq-server
    affected: no fix planned “Out of support scope”
  • Red Hat OpenStack Platform 18.0 rabbitmq-server
    affected: no fix available “Fix deferred”
  • Red Hat Hardened Images rabbitmq-server4.3 4.3.6-1.hum1
    fixed: vendor fix RHSA-2026:67552

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
40 d ago

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-w9hf-476r-443x referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 6.3 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
CNA 4.0 6.3 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
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
bitnami rabbitmq
>=4.0.0, <4.0.23
>=4.1.0, <4.1.14
>=4.2.0, <4.2.9
>=4.3.0, <4.3.3
4.0.23
4.1.14
4.2.9
4.3.3

Affected products

  • rabbitmq rabbitmq-server

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.