# CVE-2026-26118: Azure MCP Server Tools Elevation of Privilege Vulnerability

> An authorized attacker can exploit Server-Side Request Forgery in Azure MCP Server Tools to elevate privileges over the network.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Mar 2026
- **Updated:** 19 Jun 2026
- **Also known as:** GHSA-hhfx-wfvq-7g9c, PYSEC-2026-2669

## What is CVE-2026-26118?

CVE-2026-26118 is a high-severity server-side request forgery vulnerability in Microsoft Azure MCP Server Tools 1.0.0 (NuGet), published on 10 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-26118?

11 open source packages ship an affected version, including Azure.Mcp, msmcp-azure and @azure/mcp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Azure.Mcp` | NuGet | From 1.0.0 | 1.0.2 |
| `Azure.Mcp` | NuGet | From 1.0.0 | 1.0.2 |
| `Azure.Mcp` | NuGet | From 2.0.0-beta.1 | 2.0.0-beta.17 |
| `Azure.Mcp` | NuGet | From 2.0.0-beta.1 | 2.0.0-beta.17 |
| `msmcp-azure` | PyPI | From 2.0.0b14 | 2.0.0b17 |
| `msmcp-azure` | PyPI | From 2.0.0b14 | 2.0.0b17 |
| `msmcp-azure` | PyPI | From 2.0.0b14 | 2.0.0b17 |
| `@azure/mcp` | npm | From 1.0.0 | 1.0.2 |
| `@azure/mcp` | npm | From 1.0.0 | 1.0.2 |
| `@azure/mcp` | npm | From 2.0.0-beta.1 | 2.0.0-beta.17 |
| `@azure/mcp` | npm | From 2.0.0-beta.1 | 2.0.0-beta.17 |

Products: Microsoft Azure Mcp Server.

## How do I fix CVE-2026-26118?

Upgrade Azure.Mcp to a fixed version for your release line: 1.0.2 or 2.0.0-beta.17.

## Is CVE-2026-26118 being exploited?

There is no known exploitation of CVE-2026-26118 in the wild and no public exploit code.

Public exploit code:

- 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. (github_poc): https://github.com/j-dahl7/mcp-attack-detection-sentinel

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26118 and fix it if it is affected.

What it is: CVE-2026-26118 is a high-severity server-side request forgery vulnerability in Microsoft Azure MCP Server Tools 1.0.0 (NuGet), published on 10 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26118 in the wild and no public exploit code.

Affected packages and fixed versions:
- Azure.Mcp (NuGet): affected from 1.0.0; fixed in 1.0.2
- Azure.Mcp (NuGet): affected from 1.0.0; fixed in 1.0.2
- Azure.Mcp (NuGet): affected from 2.0.0-beta.1; fixed in 2.0.0-beta.17
- Azure.Mcp (NuGet): affected from 2.0.0-beta.1; fixed in 2.0.0-beta.17
- msmcp-azure (PyPI): affected from 2.0.0b14; fixed in 2.0.0b17
- msmcp-azure (PyPI): affected from 2.0.0b14; fixed in 2.0.0b17
- msmcp-azure (PyPI): affected from 2.0.0b14; fixed in 2.0.0b17
- @azure/mcp (npm): affected from 1.0.0; fixed in 1.0.2
- @azure/mcp (npm): affected from 1.0.0; fixed in 1.0.2
- @azure/mcp (npm): affected from 2.0.0-beta.1; fixed in 2.0.0-beta.17
- @azure/mcp (npm): affected from 2.0.0-beta.1; fixed in 2.0.0-beta.17

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26118/ (Markdown: https://insights.sbomify.com/CVE-2026-26118/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26118
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26118
- OSV: https://osv.dev/vulnerability/CVE-2026-26118

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26118/
Summaries are generated and may contain mistakes; the official description above is the record.