MCP TypeScript SDK: Experimental tasks were not tied to the session that created them
High severity
GitHub Reviewed
Published
Oct 2, 2026
in
modelcontextprotocol/typescript-sdk
•
Updated Oct 20, 2026
Package
Affected versions
>= 1.24.0, < 1.32.0
Patched versions
1.32.0
Description
Published to the GitHub Advisory Database
Oct 20, 2026
Reviewed
Oct 20, 2026
Last updated
Oct 20, 2026
Summary
In affected versions, the experimental tasks feature (
taskStore) did not check which session created a task. Clients sharing oneInMemoryTaskStorecould 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
taskStoretoMcpServerorServer. Ifgrep -ri taskstore --exclude-dir=node_modules .finds nothing, you are not affected.Affected versions:
@modelcontextprotocol/sdk1.24.0 through 1.31.0. The 2.x packages are not affected.Fix
Upgrade to
@modelcontextprotocol/sdk1.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 oneInMemoryTaskStoreper session.References