Skip to content
Cloud

CVE-2026-26118

8.8
High
EPSS 0.96%Patch availableMar 11, 2026

SSRF in Azure MCP Server enables privilege escalation.

common questions

Is CVE-2026-26118 being exploited?

Not confirmed. CVE-2026-26118 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.96% probability of exploitation in the next 30 days.

How severe is CVE-2026-26118?

CVE-2026-26118 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-26118?

Yes. A fix has been recorded for CVE-2026-26118. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-26118 affect?

CVE-2026-26118 affects Azure MCP Server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-26118?

Patch when released; restrict MCP exposure and monitor activity.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Azure MCP Server
impact

Authorized SSRF allows network-wide privilege escalation on MCP Server; could access restricted resources.

action required

Patch when possible

affected versions
Microsoft Azure MCP Server Tools 1.0.0 (npm)
  • affected>= 1.0.0 and < 1.0.2
Microsoft Azure MCP Server Tools 1.0.0 (NuGet)
  • affected>= 1.0.0 and < 1.0.2
Microsoft Azure MCP Server Tools 2.0.0 (npm)
  • affected>= 2.0.0-beta.1 and < 2.0.0-beta.17
Microsoft Azure MCP Server Tools 2.0.0 (NuGet)
  • affected>= 2.0.0-beta.1 and < 2.0.0-beta.17
Microsoft Azure MCP Server Tools 2.0.0 (PyPi)
  • affected>= 2.0.0-beta.1 and < 2.0.0-beta.17

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free