dbcve.org
Azure Mcp ServerApplication · Microsoft

CVE-2026-26118

HIGH · 8.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 2.0.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Server-side request forgery (SSRF) vulnerability in Azure MCP Server enables an authorized attacker to induce the server to make arbitrary network requests, potentially accessing internal services, cloud metadata endpoints, or bypassing network segmentation to elevate privileges.

MitigationApply Microsoft's security patch when available; implement network segmentation and restrict outbound connectivity from the MCP Server to minimize exposure; monitor for unusual outbound requests to internal/cloud metadata addresses.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Azure Mcp ServerApplication
Affected:< 2.0.0= 2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Azure MCP Server is deployed
    Review your installed applications, containers, or services for Microsoft Azure MCP Server. Check running processes or deployed resources in your Azure environment for 'mcp', 'mcp server', or 'Model Context Protocol' related components.
    Affected if Azure MCP Server is present in the environment
  2. Determine the installed version
    Run 'dotnet list package' for .NET deployments, check the installed package version in your dependency manifest, or query the MCP Server service version if exposed via --version flag. Compare against the affected range: versions < 2.0.0 and = 2.0.0.
    Affected if The installed version is 2.0.0 or any earlier version (versions prior to 2.0.1)
  3. Verify the MCP Server is accessible to network requests
    Check if the MCP Server is exposed on a network interface or port that accepts incoming connections. Review firewall rules, network security groups, or reverse proxy configurations that allow external or internal clients to reach the MCP Server service.
    Affected if The MCP Server is network-accessible to authorized users or applications
  4. Check for unusual outbound network activity
    Review network logs, proxy logs, or Azure Network Watcher flow logs for outbound requests from the MCP Server host to internal IP ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) or cloud metadata endpoints (169.254.169.254 for Azure).
    Affected if The server is making outbound requests to internal or metadata addresses that were not intentionally configured

You are affected if Azure MCP Server is running and the installed version is 2.0.0 or any earlier version, especially if the service is network-accessible to authorized attackers who could exploit the SSRF to make arbitrary requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.0 or later
Fixed in 2.0.0
Interim mitigation

Apply Microsoft's security patch when available; implement network segmentation and restrict outbound connectivity from the MCP Server to minimize exposure; monitor for unusual outbound requests to internal/cloud metadata addresses.

Recommended fix Moderate confidence

Azure MCP Server >= 2.0.1

  1. 1. Identify current Azure MCP Server version using 'az mcp version' or checking installed packages
  2. 2. Download or install Azure MCP Server version 2.0.1 or later from official Microsoft sources
  3. 3. Backup current configuration files before upgrading
  4. 4. Stop the Azure MCP Server service
  5. 5. Install the updated version (e.g., 'pip install azure-mcp-server>=2.0.1' or use appropriate package manager)
  6. 6. Verify the installation succeeded by checking the version
  7. 7. Start the Azure MCP Server service
  8. 8. Test that SSRF vulnerability is remediated by verifying the server no longer makes arbitrary HTTP requests to unauthorized internal resources
Caveat Review release notes for any breaking changes between 2.0.0 and the target version; ensure compatibility with dependent components

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Azure Mcp Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26118 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26118 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data