CVE-2026-26118

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 1.0%, top 41% 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: cna:microsoft, epss
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Server-side request forgery (ssrf) in Azure MCP Server allows an authorized attacker to elevate privileges over a network.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
56(Track)
EG Risk 56/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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
59%
KEV
Not listed

Published

March 10, 2026

Last Modified

June 19, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-26118

Vendor Advisories for CVE-2026-26118(1)

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

Affected Packages

(3 across 3 ecosystems)
npm(1)
PackageVulnerable rangeFixed inDependents
@azure/mcp—1.0.2—
NuGet(1)
PackageVulnerable rangeFixed inDependents
Azure.Mcp1.0.0, 1.0.11.0.2—
PyPI(1)
PackageVulnerable rangeFixed inDependents
msmcp-azure2.0.0b14, 2.0.0b15, 2.0.0b162.0.0b17—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 50× 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 110 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCj-dahl7/mcp-attack-detection-sentinel
    First seen Mar 17, 2026

    Sentinel detection lab for MCP attack chains: CVE-2026-26118 SSRF token theft, tool poisoning, cross-server exfiltration, identity post-exploitation. Maps to OWASP Agentic Top 10. 5 analytics rules, 7 hunting queries, workbook. Companion to nineliveszerotrust.com.

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-26118?
CVE-2026-26118 is a high vulnerability published on March 10, 2026. Server-side request forgery (ssrf) in Azure MCP Server allows an authorized attacker to elevate privileges over a network.
When was CVE-2026-26118 disclosed?
CVE-2026-26118 was first published in the National Vulnerability Database on March 10, 2026, with the most recent update on June 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-26118 actively exploited?
CVE-2026-26118 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 41.1% of all scored CVEs.
What is the CVSS score of CVE-2026-26118?
CVE-2026-26118 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-26118?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26118, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-26118

Explore →

Is Your Infrastructure Affected by CVE-2026-26118?

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

Start Free Scan →Browse All CVEs