CVE-2026-26118

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.9% (58th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
Elevated
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 8.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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.8HIGHmedium confidence
EG Risk
56
EG Risk 56/100

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 (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
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 none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.9%
EPSS %ILE
58th
KEV
Not listed

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 none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

March 10, 2026

Last Modified

June 19, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
Patch available. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

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 rangeFix by version rangeDependents
@azure/mcp—
  • 2.0.0-beta.1 up to 2.0.0-beta.17: fixed in 2.0.0-beta.17
  • 1.0.0 up to 1.0.2: fixed in 1.0.2
—
NuGet(1)
PackageVulnerable rangeFix by version rangeDependents
Azure.Mcp1.0.0, 1.0.1
  • 2.0.0-beta.1 up to 2.0.0-beta.17: fixed in 2.0.0-beta.17
  • 1.0.0 up to 1.0.2: fixed in 1.0.2
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
msmcp-azure—
  • 2.0.0b14 up to 2.0.0b17: fixed in 2.0.0b17
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 24× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 94 of 144 refreshes 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 50 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Public detection checks

(1 reference)

A public detection check is referenced for this CVE (1 GitHub checker repository). A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code.

  • GitHub checkerj-dahl7/mcp-attack-detection-sentinel
    Published 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 CWE)

Frequently asked(5)

What is CVE-2026-26118?
CVE-2026-26118 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-26118 was made public on March 10, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on March 10, 2026. EchelonGraph's copy of the record carries a last-modified date of June 19, 2026; the record at its source may have been updated since.
Is CVE-2026-26118 actively exploited?
CVE-2026-26118 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-26118?
CVE-2026-26118 has a CVSS base score of 8.8 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-26118?
A fix for CVE-2026-26118 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-26118 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-26118

Explore →

Is Your Infrastructure Affected by CVE-2026-26118?

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

Book a Demo →Browse All CVEs