Browse / MCP and Tool Server Flaws / CVE-2026-111767
MCP TypeScript SDK: Experimental tasks were not tied to the session that created them
- Class
- MCP and Tool Server Flaws (filed by a model that read the advisory)
- Technique
- Authentication and access control
- Affected
- @modelcontextprotocol/sdk (npm)
- CVSS
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
- EPSS
- 0.3% chance of exploitation in 30 days
How it works, in short
The MCP TypeScript SDK's experimental task store did not tie tasks to their creating session, letting other clients list, read and cancel them. (Our summary, written by a model. The source text is below.)
Details
Summary
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.
Am I affected?
Only if your HTTP server passes taskStore to McpServer or Server. If grep -ri taskstore --exclude-dir=node_modules . finds nothing, you are not affected.
Affected versions: @modelcontextprotocol/sdk 1.24.0 through 1.31.0. The 2.x packages are not affected.
Fix
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.
References
- https://github.com/modelcontextprotocol/typescript-sdk/security/advisories/GHSA-22jm-h49p-29qw
- https://github.com/modelcontextprotocol/typescript-sdk/pull/2925
- https://github.com/modelcontextprotocol/typescript-sdk/commit/727075b5bbeb77fbea22041b36b72a73042160fa
- https://github.com/modelcontextprotocol/typescript-sdk
Source: GitHub Advisory Database, used under CC BY 4.0.