CVE-2026-61837

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (14th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.3Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity63% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
14th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

September 29, 2026

Advisory Details (5)

Auto-updated Sep 25, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

RabbitMQ 4.3.3

Patch available: rabbitmq/rabbitmq-server v4.3.3

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3
github_release Patch Available

RabbitMQ 4.2.9

Patch available: rabbitmq/rabbitmq-server v4.2.9

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9
github_commit

commit b94004dea530 (rabbitmq/rabbitmq-server)

Fix landed in rabbitmq/rabbitmq-server commit b94004dea530 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/commit/b94004dea530f961b3dc649d94969b89f1a3183f
github_commit

commit 341e3f2795eb (rabbitmq/rabbitmq-server)

Fix landed in rabbitmq/rabbitmq-server commit 341e3f2795eb — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/commit/341e3f2795ebd1f816e712530f651a3221d23ad9
github Patch Available🟡 PoC Available

AMQP 1.0 management `GET /bindings` exposes full binding topology to any authenticated AMQP user without resource/management permission checks · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-w9hf-476r-443x

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-03 23:39 UTCEG score recompute
  2. 2026-10-03 14:26 UTCEPSS rescore
  3. 2026-10-02 22:51 UTCEG score recompute
  4. 2026-10-02 17:56 UTCEPSS rescore
  5. 2026-10-01 22:06 UTCEG score recompute
  6. 2026-10-01 19:50 UTCEPSS rescore
  7. 2026-09-30 21:18 UTCEG score recompute
  8. 2026-09-30 15:03 UTCEPSS rescore
  9. 2026-09-29 20:31 UTCEG score recompute
  10. 2026-09-29 19:38 UTCEG score recompute
  11. 2026-09-29 15:29 UTCEG score recompute
  12. 2026-09-28 14:44 UTCEG score recompute
  13. 2026-09-28 13:51 UTCEPSS rescore
  14. 2026-09-26 18:21 UTCEG score recompute
  15. 2026-09-26 15:59 UTCEPSS rescore
  16. 2026-09-25 17:34 UTCEG score recompute
  17. 2026-09-25 16:39 UTCEG score recompute
  18. 2026-09-25 16:39 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61837?
CVE-2026-61837 is a medium vulnerability published on September 25, 2026. 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…
When was CVE-2026-61837 disclosed?
CVE-2026-61837 was first published on September 25, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61837 actively exploited?
CVE-2026-61837 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61837?
CVE-2026-61837 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61837?
A fix for CVE-2026-61837 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-61837

Explore →

Is Your Infrastructure Affected by CVE-2026-61837?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs