UTC
High

MCP TypeScript SDK: Experimental tasks were not tied to the session that created them

CVE-2026-111767 · GHSA-22jm-h49p-29qw · published 2026-10-20

Severity
High
CVSS score
8.6
Chance of exploitation (EPSS)
0.34%
Fixed in
1.32.0
  • Exploitation No known exploitation
  • Automatable Yes
  • Technical impact Partial
  • CISA SSVC
What it is

In affected versions, the experimental tasks feature (taskStore) did not check which session created a task. Clients sharing one InMemoryTaskStore could list, read and cancel each other's tasks. Experimental tasks are deprecated. The 2026-07-28 specification replaced them with a redesigned extension. The best course of action is to stop using them.

What to do

Upgrade @modelcontextprotocol/sdk to 1.32.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Upgrade to @modelcontextprotocol/sdk 1.32.0 or later. Each task is now tied to the session that created it, so a client that starts a new session can no longer reach its earlier tasks. If you cannot upgrade yet, remove taskStore, or create one InMemoryTaskStore per session.

Affected
PackageRegistryAffectedFixed in
@modelcontextprotocol/sdknpm>= 1.24.0, < 1.32.01.32.0
Downstream in the Official MCP Registry

315 registered MCP servers install an affected version today, by the dependency versions a fresh install resolves.

  • ai.kloudy/kloudy@modelcontextprotocol/sdk@1.31.0
  • ai.makerportal/compute@modelcontextprotocol/sdk@1.30.0
  • ai.maxwellinternational/data@modelcontextprotocol/sdk@1.31.0
  • ai.mentu/navigator@modelcontextprotocol/sdk@1.29.0
  • ai.myspaice/spaces@modelcontextprotocol/sdk@1.29.0
  • ai.sanctuaryprotocol/sanctuary@modelcontextprotocol/sdk@1.30.0
  • ai.satohub/kit@modelcontextprotocol/sdk@1.30.1
  • ai.sendshort/sendshort@modelcontextprotocol/sdk@1.30.0
  • app.somiya/mcp@modelcontextprotocol/sdk@1.30.0
  • cheap.doc/mcp@modelcontextprotocol/sdk@1.31.0
  • cn.housingsentinel/housing-sentinel@modelcontextprotocol/sdk@1.29.0
  • com.apideck/mcp@modelcontextprotocol/sdk@1.25.2
All 315 servers on the trace →

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].