← Back
CVE-2026-26118
SSRF (Server-Side Request Forgery) in msmcp-azure (CVE-2026-26118)
Summary
SSRF in msmcp-azure (CVE-2026-26118). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `2.0.0b17` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-26118** has been found in msmcp-azure.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade msmcp-azure to **2.0.0b17** or later.
If unsure, ask your IT team or search "msmcp-azure CVE-2026-26118" on the vendor's site.
CVE-2026-26118 (msmcp-azure) — CWE-918 /
Attack vector: remote (network-reachable) / no user interaction
Patched: `2.0.0b17` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**SSRF** (CWE-918) exists in msmcp-azure.
📍 Affected scope
msmcp-azure — .
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.0.0b17**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'msmcp-azure' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'msmcp-azure' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `msmcp-azure` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade msmcp-azure to 2.0.0b17ステージング環境で 2.0.0b17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
msmcp-azure
[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0b14"},{"fixed":"2.0.0b17"}]}]
NuGet
Azure.Mcp
[{"type":"ECOSYSTEM","events":[{"introduced":"1.0.0"},{"fixed":"1.0.2"}]}]
npm
@azure/mcp
[{"type":"SEMVER","events":[{"introduced":"1.0.0"},{"fixed":"1.0.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-26118
- advisory https://github.com/advisories/GHSA-hhfx-wfvq-7g9c
- package https://github.com/microsoft/mcp
- package https://pypi.org/project/msmcp-azure
- web https://github.com/microsoft/mcp/commit/804ff60293206c4d8e832f772097238561bf2c34
- web https://github.com/microsoft/mcp/releases/tag/Azure.Mcp.Server-1.0.2
- web https://github.com/microsoft/mcp/releases/tag/Azure.Mcp.Server-2.0.0-beta.17
- web https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-26118