Vulnerability in mcp (CVE-2026-52870)
Summary
Vulnerability in mcp (CVE-2026-52870). Confidential information can be exposed externally. Exploitable via TaskStore. Mitigation: upgrade to 1.27.2 or later.
Original description
The description as published by the source.
The MCP Python SDK, called mcp on PyPI, is a Python implementation of the Model Context Protocol (MCP). From 1.23.0 until 1.27.2, default handlers installed by server.experimental.enable_tasks() for tasks/list, tasks/get, tasks/result, and tasks/cancel operate only on task identifiers without recording the session that created each task, allowing any connected client to enumerate, read results from, consume messages for, or cancel other clients' tasks. This issue is fixed in version 1.27.2.
Source: NIST National Vulnerability Database 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-52870 has been found in mcp.
Attackers can target a specific entry point like TaskStore over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.6/10.
What to do: upgrade mcp to 1.27.2 or later.
If unsure, ask your IT team or search "mcp CVE-2026-52870" on the vendor's site.
CVE-2026-52870 (mcp) — CWE-862 / CVSS v3 7.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: TaskStore
Patched: 1.27.2 — 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-862) exists in mcp. Attackers reach the vulnerable code path via TaskStore.
Check the vendor advisory for the affected versions of mcp. Attack surface: TaskStore.
Severity: High (CVSS 7.6/10). Confidential information can be exposed externally.
Update to 1.27.2.
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 '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 'mcp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mcpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mcp to 1.27.2ステージング環境で 1.27.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- advisory github.com
- package github.com
- package pypi.org
- patch github.com
- patch github.com
- web github.com