Skip to main content
Public proof of conceptFix available

CVE-2026-26118

A public proof of concept exists; no exploitation attested.

  • Published2026-03-10
  • Fixed in2.0.0-beta.17 · 1.0.2
  • WeaknessCWE-918

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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

Timeline

dates in UTC
  1. 2026-03-1018:18CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub

Versions per branch

OSV · NVD
@azure/mcp
BranchAffectedFixed in
2.0≥ 2.0.0-beta.1, < 2.0.0-beta.172.0.0-beta.17
1.0≥ 1.0.0, < 1.0.21.0.2
Microsoft azure mcp server
BranchAffectedFixed in
2.0< 2.0.02.0.0
2.0= 2.0.0no fix published
Azure.Mcp
BranchAffectedFixed in
2.0≥ 2.0.0-beta.1, < 2.0.0-beta.172.0.0-beta.17
1.0≥ 1.0.0, < 1.0.21.0.2

1 more product in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA5 products

As microsoft, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Microsoft Azure MCP Server Tools 1.0.0 (npm)
    Affected
    • ≥ 1.0.0, < 1.0.2fixed in 1.0.2custom
  • Microsoft Azure MCP Server Tools 1.0.0 (NuGet)
    Affected
    • ≥ 1.0.0, < 1.0.2fixed in 1.0.2custom
  • Microsoft Azure MCP Server Tools 2.0.0 (npm)
    Affected
    • ≥ 2.0.0-beta.1, < 2.0.0-beta.17fixed in 2.0.0-beta.17custom
  • Microsoft Azure MCP Server Tools 2.0.0 (NuGet)
    Affected
    • ≥ 2.0.0-beta.1, < 2.0.0-beta.17fixed in 2.0.0-beta.17custom
  • Microsoft Azure MCP Server Tools 2.0.0 (PyPi)
    Affected
    • ≥ 2.0.0-beta.1, < 2.0.0-beta.17fixed in 2.0.0-beta.17custom

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-06-19

Fix

  1. Update @azure/mcp to 2.0.0-beta.17 · 1.0.2

Advisories and patches

Detection

read 2026-11-01 01:02 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2026-03-10
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-hhfx-wfvq-7g9c

Frequently asked questions

What is CVE-2026-26118?

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

Is CVE-2026-26118 actively exploited?

Active exploitation of CVE-2026-26118 has not been confirmed. Its EPSS score was 1.1% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-26118?

CVE-2026-26118 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running @azure/mcp? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record