CVE-2026-57211

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.6% (50th 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-43016 (ENISA EUVD)Source: ENISA EUVD

10.0EG
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.6%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

RabbitMQ is a messaging and streaming broker. Prior to 4.1.11 and 4.2.6 on Windows, the RabbitMQ management plugin static file handler rabbit_mgmt_wm_static can pass URL-encoded backslashes to erl_prim_loader:read_file_info before path validation when multiple management extension plugins are enabled, causing outbound DNS and SMB requests to attacker-controlled UNC paths. This issue is fixed in versions 4.1.11 and 4.2.6.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
61
EG Risk 61/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 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.6%
EPSS %ILE
50th
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-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.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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

July 10, 2026

Last Modified

October 25, 2026

Advisory Details (5)

Auto-updated Nov 8, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

UNC SSRF affecting RabbitMQ management UI on Windows · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-7v84-m3g5-vxq6
GitHub release Patch Available

RabbitMQ 4.2.6

Patch available: rabbitmq/rabbitmq-server v4.2.6

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6
GitHub pull request

Management plugin: apply path filtering earlier

Fix merged in rabbitmq/rabbitmq-server PR #15803 on 2026-03-23 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/pull/15803
GitHub commit

commit 6730797f6a34 (rabbitmq/rabbitmq-server)

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

https://github.com/rabbitmq/rabbitmq-server/commit/6730797f6a34b4e8308cea60adf1243857e70204
GitHub commit

commit 39c3a8e9c71d (rabbitmq/rabbitmq-server)

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

https://github.com/rabbitmq/rabbitmq-server/commit/39c3a8e9c71da0403d8dfc13f700e60c936e3682

Vendor Advisories for CVE-2026-57211(3)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrabbitmq-server4-3-main-4.3.2-1.hum12026-07-06redhat
redhatrabbitmq-server4-2-main-4.2.8-1.hum12026-07-06redhat

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.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 63× 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.

Showing the most recent 100 of 438 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 338 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 19:02 UTCEchelonGraph re-scored
  2. 2026-11-12 19:02 UTCVendor advisory
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  4. 2026-11-11 21:18 UTCEchelonGraph re-scored
  5. 2026-11-11 21:18 UTCVendor advisory
  6. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  7. 2026-11-10 23:35 UTCEchelonGraph re-scored
  8. 2026-11-10 23:35 UTCVendor advisory
  9. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  10. 2026-11-10 01:50 UTCEchelonGraph re-scored
  11. 2026-11-10 01:50 UTCVendor advisory
  12. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  13. 2026-11-09 04:07 UTCEchelonGraph re-scored
  14. 2026-11-09 04:07 UTCVendor advisory
  15. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  16. 2026-11-08 06:20 UTCEchelonGraph re-scored
  17. 2026-11-08 06:20 UTCVendor advisory
  18. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  19. 2026-11-07 08:36 UTCEchelonGraph re-scored
  20. 2026-11-07 08:36 UTCVendor advisory
  21. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  22. 2026-11-06 12:55 UTCOSV refresh
  23. 2026-11-06 10:53 UTCEchelonGraph re-scored
  24. 2026-11-06 10:53 UTCVendor advisory
  25. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.6% · 50th percentile
Show 75 more
  1. 2026-11-05 13:10 UTCEchelonGraph re-scored
  2. 2026-11-05 13:10 UTCVendor advisory
  3. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  4. 2026-11-04 15:24 UTCVendor advisory
  5. 2026-11-03 17:40 UTCEchelonGraph re-scored
  6. 2026-11-03 17:40 UTCVendor advisory
  7. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  8. 2026-11-02 19:57 UTCEchelonGraph re-scored
  9. 2026-11-02 19:57 UTCVendor advisory
  10. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  11. 2026-11-01 22:13 UTCEchelonGraph re-scored
  12. 2026-11-01 22:13 UTCVendor advisory
  13. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  14. 2026-11-01 00:28 UTCEchelonGraph re-scored
  15. 2026-11-01 00:28 UTCVendor advisory
  16. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  17. 2026-10-31 02:46 UTCEchelonGraph re-scored
  18. 2026-10-31 02:46 UTCVendor advisory
  19. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  20. 2026-10-30 05:02 UTCEchelonGraph re-scored
  21. 2026-10-30 05:02 UTCVendor advisory
  22. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  23. 2026-10-29 07:19 UTCEchelonGraph re-scored
  24. 2026-10-29 07:19 UTCVendor advisory
  25. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  26. 2026-10-28 09:37 UTCEchelonGraph re-scored
  27. 2026-10-28 09:37 UTCVendor advisory
  28. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  29. 2026-10-27 11:04 UTCEchelonGraph re-scored
  30. 2026-10-27 11:04 UTCVendor advisory
  31. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  32. 2026-10-26 13:21 UTCEchelonGraph re-scored
  33. 2026-10-26 13:21 UTCVendor advisory
  34. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  35. 2026-10-25 15:26 UTCVendor advisory
  36. 2026-10-25 14:17 UTCEchelonGraph re-scored
  37. 2026-10-24 18:34 UTCEchelonGraph re-scored
  38. 2026-10-24 18:34 UTCVendor advisory
  39. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  40. 2026-10-23 20:49 UTCEchelonGraph re-scored
  41. 2026-10-23 20:49 UTCVendor advisory
  42. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  43. 2026-10-22 23:01 UTCEchelonGraph re-scored
  44. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  45. 2026-10-22 01:17 UTCEchelonGraph re-scored
  46. 2026-10-22 01:17 UTCVendor advisory
  47. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  48. 2026-10-21 03:20 UTCEchelonGraph re-scored
  49. 2026-10-21 03:20 UTCVendor advisory
  50. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  51. 2026-10-20 05:23 UTCEchelonGraph re-scored
  52. 2026-10-20 05:23 UTCVendor advisory
  53. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  54. 2026-10-19 06:46 UTCEchelonGraph re-scored
  55. 2026-10-19 06:46 UTCVendor advisory
  56. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  57. 2026-10-18 08:58 UTCVendor advisory
  58. 2026-10-18 03:29 UTCEchelonGraph re-scored
  59. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  60. 2026-10-17 10:28 UTCEchelonGraph re-scored
  61. 2026-10-17 10:28 UTCVendor advisory
  62. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  63. 2026-10-16 12:20 UTCEchelonGraph re-scored
  64. 2026-10-16 12:20 UTCVendor advisory
  65. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  66. 2026-10-15 13:56 UTCEchelonGraph re-scored
  67. 2026-10-15 13:56 UTCVendor advisory
  68. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  69. 2026-10-14 08:48 UTCEchelonGraph re-scored
  70. 2026-10-14 08:48 UTCVendor advisory
  71. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  72. 2026-10-13 04:31 UTCEchelonGraph re-scored
  73. 2026-10-13 04:31 UTCVendor advisory
  74. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  75. 2026-10-12 15:54 UTCEchelonGraph re-scored

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-57211?
CVE-2026-57211 is a critical-severity vulnerability; its CVE record was published on July 10, 2026. RabbitMQ is a messaging and streaming broker. Prior to 4.1.11 and 4.2.6 on Windows, the RabbitMQ management plugin static file handler rabbit_mgmt_wm_static can pass URL-encoded backslashes to erl_prim_loader:read_file_info before path validation when multiple management extension plugins are…
When was the CVE record for CVE-2026-57211 published?
The CVE record for CVE-2026-57211 was published on July 10, 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 25, 2026; the record at its source may have been updated since.
Is CVE-2026-57211 actively exploited?
CVE-2026-57211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57211?
CVE-2026-57211 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-57211?
A fix for CVE-2026-57211 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57211 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-57211?

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

Book a Demo →Browse All CVEs