For your digest
Azure.Mcp, @azure/mcp: Azure MCP Server has Server-Side Request Forgery issue that allows authorized attacker to elevate privileges over a…
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- Azure.Mcp (NuGet): from 2.0.0-beta.1, before 2.0.0-beta.17
- Azure.Mcp (NuGet): from 1.0.0, before 1.0.2
- @azure/mcp (npm): from 2.0.0-beta.1, before 2.0.0-beta.17
- msmcp-azure (PyPI): from 2.0.0b14, before 2.0.0b17
- @azure/mcp (npm): from 1.0.0, before 1.0.2
- msmcp-azure (PyPI): from 2.0.0b14, before 2.0.0b17
The fix
Azure.Mcp (NuGet) fixed in 2.0.0-beta.17
dotnetdotnet add package Azure.Mcp --version 2.0.0-beta.17Check what is installeddotnet list packagePaste into Cursor, Lovable or Claude CodeUpgrade the NuGet dependency Azure.Mcp to 2.0.0-beta.17 or the nearest later release, to fix CVE-2026-26118. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.Azure.Mcp (NuGet) fixed in 1.0.2
dotnetdotnet add package Azure.Mcp --version 1.0.2Check what is installeddotnet list packagePaste into Cursor, Lovable or Claude CodeUpgrade the NuGet dependency Azure.Mcp to 1.0.2 or the nearest later release, to fix CVE-2026-26118. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@azure/mcp (npm) fixed in 2.0.0-beta.17
npmnpm install "@azure/mcp@2.0.0-beta.17"pnpmpnpm add "@azure/mcp@2.0.0-beta.17"yarnyarn add "@azure/mcp@2.0.0-beta.17"bunbun add "@azure/mcp@2.0.0-beta.17"Check what is installednpm ls @azure/mcpPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @azure/mcp to 2.0.0-beta.17 or the nearest later release, to fix CVE-2026-26118. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@azure/mcp (npm) fixed in 1.0.2
npmnpm install "@azure/mcp@1.0.2"pnpmpnpm add "@azure/mcp@1.0.2"yarnyarn add "@azure/mcp@1.0.2"bunbun add "@azure/mcp@1.0.2"Check what is installednpm ls @azure/mcpPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @azure/mcp to 1.0.2 or the nearest later release, to fix CVE-2026-26118. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.msmcp-azure (PyPI) fixed in 2.0.0b17
pippython -m pip install msmcp-azure==2.0.0b17uvuv add msmcp-azure==2.0.0b17poetrypoetry add msmcp-azure@2.0.0b17Check what is installedpython -m pip show msmcp-azurePaste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency msmcp-azure to 2.0.0b17 or the nearest later release, to fix CVE-2026-26118. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".