Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.8amended

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

CVE-2026-26118GHSA-hhfx-wfvq-7g9c

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (msmcp-azure 2.0.0b17; @azure/mcp 2.0.0-beta.17, 1.0.2; azure.mcp 2.0.0-beta.17, 1.0.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI msmcp-azure

    Affected
    >= 2.0.0b14, < 2.0.0b17
    Fixed in
    2.0.0b17

  • npm @azure/mcp

    Affected
    >= 2.0.0-beta.1, < 2.0.0-beta.17>= 1.0.0, < 1.0.2
    Fixed in
    1.0.2, 2.0.0-beta.17

  • NuGet azure.mcp

    Affected
    >= 2.0.0-beta.1, < 2.0.0-beta.17>= 1.0.0, < 1.0.2
    Fixed in
    1.0.2, 2.0.0-beta.17

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-26118: 1.00% estimated exploitation activity in the next 30 days; percentile 62.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-hhfx-wfvq-7g9c

  2. Revision 1 · created ·

    Published from osv record GHSA-hhfx-wfvq-7g9c

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-26118

Advisory: Azure MCP Server has Server-Side Request Forgery issue that allows authorized attacker to elevate privileges over a network
IDs: CVE-2026-26118, GHSA-hhfx-wfvq-7g9c
Record: https://patchnext.com/advisories/cve-2026-26118 (revision 2, source checked 26 Oct 2026, 12:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: msmcp-azure 2.0.0b17; @azure/mcp 2.0.0-beta.17, 1.0.2; azure.mcp 2.0.0-beta.17, 1.0.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI msmcp-azure: affected >= 2.0.0b14, < 2.0.0b17; fixed in 2.0.0b17
- npm @azure/mcp: affected >= 2.0.0-beta.1, < 2.0.0-beta.17; >= 1.0.0, < 1.0.2; fixed in 1.0.2, 2.0.0-beta.17
- NuGet azure.mcp: affected >= 2.0.0-beta.1, < 2.0.0-beta.17; >= 1.0.0, < 1.0.2; fixed in 1.0.2, 2.0.0-beta.17

## Suggested inspection (read-only)
- `python -m pip show msmcp-azure`: prints the installed version. Run with the environment that serves production active.
- `npm ls @azure/mcp --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- NuGet azure.mcp: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on msmcp-azure, @azure/mcp, azure.mcp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-hhfx-wfvq-7g9c (OSV record GHSA-hhfx-wfvq-7g9c lists affected ranges: NuGet azure.mcp >=2.0.0-beta.1 =1.0.0 =2.0.0-beta.1 =1.0.0 =2.0.0b14 <2.0.0b17 (fixed))
- Verified: https://github.com/advisories/GHSA-hhfx-wfvq-7g9c (GitHub-reviewed advisory GHSA-hhfx-wfvq-7g9c lists affected ranges: NuGet azure.mcp >=2.0.0-beta.1 =1.0.0 =2.0.0-beta.1 =1.0.0 =2.0.0b14 <2.0.0b17)

Commands are suggestions: review each one before running it.

Loading voting…