CVE-2026-61837

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.3% (22nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-87227 (ENISA EUVD)Source: ENISA EUVD

5.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.3Exploit: No code on recordExposed 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
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 25, 2026

Last Modified

October 15, 2026

Advisory Details (5)

Auto-updated Sep 25, 2026
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 advisoryMentions a patch (unverified)

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

Vendor Advisories for CVE-2026-61837(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrabbitmq-server4-3-main-4.3.6-1.hum12026-09-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server3.10.8-1.1 ... 4.3.6-1 (29 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server4.0.5-10 ... 4.3.6-1 (19 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server4.0.5-10 ... 4.3.2-5 (16 versions)
  • every version up to 4.3.6-1: fixed in 4.3.6-1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  2. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  3. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  5. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  6. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  8. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  11. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-30 09:25 UTCOSV refresh
  16. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-10-25 14:14 UTCEchelonGraph re-scored
  22. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  23. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  24. 2026-10-22 19:55 UTCEchelonGraph re-scored
  25. 2026-10-22 19:55 UTCVendor advisory
Show 50 more
  1. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  2. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  3. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  4. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  5. 2026-10-18 03:25 UTCEchelonGraph re-scored
  6. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  7. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  8. 2026-10-15 20:29 UTCEchelonGraph re-scored▼ 1.00
  9. 2026-10-15 20:28 UTCNVD updateCVSS v3 → 5.3
  10. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  11. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  12. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  13. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  14. 2026-10-12 15:50 UTCEchelonGraph re-scored
  15. 2026-10-11 19:34 UTCEchelonGraph re-scored
  16. 2026-10-11 16:49 UTCEchelonGraph re-scored
  17. 2026-10-11 14:11 UTCEchelonGraph re-scored
  18. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  19. 2026-10-11 05:24 UTCEchelonGraph re-scored
  20. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  21. 2026-10-10 04:39 UTCEchelonGraph re-scored
  22. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  23. 2026-10-09 03:48 UTCEchelonGraph re-scored
  24. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  25. 2026-10-08 03:02 UTCEchelonGraph re-scored
  26. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  27. 2026-10-07 02:17 UTCEchelonGraph re-scored
  28. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  29. 2026-10-06 01:31 UTCEchelonGraph re-scored
  30. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  31. 2026-10-05 00:26 UTCEchelonGraph re-scored
  32. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  33. 2026-10-03 23:39 UTCEchelonGraph re-scored
  34. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  35. 2026-10-02 22:51 UTCEchelonGraph re-scored
  36. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  37. 2026-10-01 22:06 UTCEchelonGraph re-scored
  38. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  39. 2026-09-30 21:18 UTCEchelonGraph re-scored
  40. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  41. 2026-09-29 20:31 UTCEchelonGraph re-scored
  42. 2026-09-29 19:38 UTCEchelonGraph re-scored
  43. 2026-09-29 15:29 UTCEchelonGraph re-scored
  44. 2026-09-28 14:44 UTCEchelonGraph re-scored
  45. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  46. 2026-09-26 18:21 UTCEchelonGraph re-scored
  47. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  48. 2026-09-25 17:34 UTCEchelonGraph re-scored
  49. 2026-09-25 16:39 UTCEchelonGraph re-scoredFirst assessed: 6.3 MEDIUM
  50. 2026-09-25 16:39 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-61837?
CVE-2026-61837 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-61837 published?
The CVE record for CVE-2026-61837 was published on September 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2026-61837 actively exploited?
CVE-2026-61837 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61837?
CVE-2026-61837 has a CVSS v3 base score of 5.3 (NVD).
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. The vendor advisories EchelonGraph has for CVE-2026-61837 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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