NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm.NET NuGet🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2026-26118 — @azure/mcp

HIGHFix: microsoft/mcp@804ff60

CVE-2026-26118 is a high-severity (CVSS 8.8) Server-Side Request Forgery (SSRF) vulnerability in @azure/mcp. A fix is available for @azure/mcp — see the affected versions and patch details below.

Azure MCP Server has Server-Side Request Forgery issue that allows authorized attacker to elevate privileges over a network

Also known asPYSEC-2026-2669
Published
Updated
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-26118.

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk+0.06%
Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk
0.00%0.52%1.04%1.56%0.0%1.1%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@azure/mcpnpm
203Kdownloads / week

Description

Server-Side Request Forgery (SSRF) in Azure MCP Server allows an authorized attacker to elevate privileges over a network.

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
📦npm@azure/mcp≥ 2.0.0-beta.1&&< 2.0.0-beta.172.0.0-beta.17npm install @azure/mcp@2.0.0-beta.17
📦npm@azure/mcp≥ 1.0.0&&< 1.0.21.0.2npm install @azure/mcp@1.0.2
.NETNuGetAzure.Mcp≥ 2.0.0-beta.1&&< 2.0.0-beta.172.0.0-beta.17dotnet add package Azure.Mcp --version 2.0.0-beta.17
.NETNuGetAzure.Mcp≥ 1.0.0&&< 1.0.21.0.2dotnet add package Azure.Mcp --version 1.0.2
🐍PyPImsmcp-azure≥ 2.0.0b14&&< 2.0.0b172.0.0b17pip install --upgrade 'msmcp-azure==2.0.0b17'

Affected Products

1 product · 17 configurations
Application
azure mcp servermicrosoft
< 2.0.0
1 version
2.0.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @azure/mcp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update @azure/mcp to 2.0.0-beta.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-26118 is resolved across your whole dependency graph.

  3. Workarounds

    Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

Server-Side Request Forgery (SSRF) in Azure MCP Server allows an authorized attacker to elevate privileges over a network.
O3 Security · Impact-Aware SCA

Is CVE-2026-26118 in your dependencies?

Find it across npm, NuGet, PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2026-26118: @azure/mcp SSRF — Fix Available