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
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.
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.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @modelcontextprotocol/sdk | npm | >= 1.24.0, < 1.32.0 | 1.32.0 |
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
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- HighMCP TypeScript SDK: HTTP server transports and handlers did not limit request body size or JSON-RPC batch length@modelcontextprotocol/hono, @modelcontextprotocol/node, @modelcontextprotocol/sdk, @modelcontextprotocol/server
- HighMCP TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation@modelcontextprotocol/sdk, @modelcontextprotocol/server
- HighMCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server@modelcontextprotocol/client, @modelcontextprotocol/sdk
- High@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse@modelcontextprotocol/sdk
- HighAnthropic's MCP TypeScript SDK has a ReDoS vulnerability@modelcontextprotocol/sdk
- HighModel Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default@modelcontextprotocol/sdk
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.