CVE-2026-57211

CRITICALNVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 52% of all CVEs by exploit prediction. 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, nvd
Trending — 3 sources updated this weekElevated
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 10.0Exploit: Elevated riskExposed: 0

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.0(medium)
EG Risk
61(Track)
EG Risk 61/100SSVC: Track

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
Severity100% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 13, 2026

Advisory Details (5)

Auto-updated Aug 25, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 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_pr

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 / EcosystemFixed in / PatchReleasedSource
redhatrabbitmq-server4-2-main-4.2.8-1.hum12026-07-06redhat
redhatrabbitmq-server4-3-main-4.3.2-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 46× in last 7d / 216× 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.

Showing the most recent 100 of 251 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-57211?
CVE-2026-57211 is a critical vulnerability 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 rabbitmgmtwmstatic can pass URL-encoded backslashes to erlprimloader:readfile_info before path validation when multiple management extension plugins are enabled,…
When was CVE-2026-57211 disclosed?
CVE-2026-57211 was first published in the National Vulnerability Database on July 10, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57211 actively exploited?
CVE-2026-57211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.5% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57211, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs