Vulnerability in windows-mcp (CVE-2026-48989)
Summary
Vulnerability in windows-mcp (CVE-2026-48989). Risk of unauthorized operations or information disclosure. Exploitable via PowerShell. Mitigation: upgrade to 0.7.5 or later.
Original description
The description as published by the source.
Windows-MCP is an open-source project that integrates AI agents with Windows. In versions prior to 0.7.5, certain HTTP modes exposed the MCP control plane without authentication while enabling wildcard CORS (allow_origins=, allow_methods=, allow_headers=*). Because the same server also exposed a PowerShell tool that executes caller-controlled commands as the Windows user running Windows-MCP, attackers could reach the control plane from arbitrary origins or non-browser clients and achieve arbitrary PowerShell execution. This issue was fixed in version 0.7.5.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48989 has been found in windows-mcp.
Attackers can target a specific entry point like PowerShell over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade windows-mcp to 0.7.5 or later.
If unsure, ask your IT team or search "windows-mcp CVE-2026-48989" on the vendor's site.
CVE-2026-48989 (windows-mcp) — CWE-306
Attack surface: PowerShell / OptionsMiddleware / CORSMiddleware / OPTIONS
Patched: 0.7.5 — 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.
A vulnerability (CWE-306) exists in windows-mcp. Attackers reach the vulnerable code path via PowerShell.
Check the vendor advisory for the affected versions of windows-mcp. Attack surface: PowerShell / OptionsMiddleware / CORSMiddleware / OPTIONS.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.7.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'windows-mcp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'windows-mcp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
windows-mcpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade windows-mcp to 0.7.5ステージング環境で 0.7.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com