boxscore/security
CVE · referencelatest edition

Reference page — cumulative record through Monday, October 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2026-61837

RabbitMQ: AMQP 1.0 management `GET /bindings` exposes full binding topology to any authenticated AMQP user without resource/management permission checks
  AV  AC  AT  PR  UI  VC  VI  VA   CVSS    EPSS   %ile   KEV
   N   L   N   L   N   N   N   N    6.3   .0026   16.1     —
AFFECTED
  Product          Versions             Fixed
  rabbitmq-server  >= 4.3.0, < 4.3.3 –  —
TIMELINE
  Jul 10  Reserved by GitHub_M
  Sep 25  Published (CNA: GitHub_M)
  Oct 15  EXPLOIT PUBLISHED — CVE-2026-61837 (rabbitmq-server). Public exploit reference added.
CWE-285, CWE-862 · CNA: GitHub_M · CVSS v4.0 · 5 references · NVD status: Analyzed

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.

Lifecycle

Complete event history — 3 events, chronological
DateEventDetail
July 10, 2026ReservedReserved by GitHub_M
September 25, 2026PublishedPublished (CNA: GitHub_M)
October 15, 2026EXPLOIT PUBLISHEDEXPLOIT PUBLISHED — CVE-2026-61837 (rabbitmq-server). Public exploit reference added.

Affected

Affected products and packages — 1 row
VendorProduct / PackageEcosystemVersion introducedFixed
rabbitmqrabbitmq-server—>= 4.3.0, < 4.3.3—

Weaknesses

CWE-285 · CWE-862

References (5)

Related

Authoritative record: CVE-2026-61837 at cve.org

Vendors: rabbitmq

Weaknesses: CWE-285 · CWE-862

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2026-61837 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Monday, October 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.