AAK-MCP-TSSDK-CVE-2026-111767-001: MCP TypeScript SDK 1.24.0 to 1.31.0: experimental tasks are not tied to the session that created them
- Severity
- HIGH
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py- Auto-fixable
- No.
- SARIF name
McpTypeScriptSdkTaskStoreSessionScope
What it detects
The official MCP TypeScript SDK (@modelcontextprotocol/sdk on npm) ships an experimental tasks feature: a server that passes a taskStore to McpServer or Server lets clients run requests as tasks and poll, list and cancel them later. From 1.24.0, where the feature and its InMemoryTaskStore first ship, until 1.32.0, every method of that store took the caller's session id and ignored it, so all clients sharing one store shared one pool of tasks: a client with a session of its own could list the tasks another session created, read their results and cancel them (CVE-2026-111767, CVSS 3.1 8.6, CWE-639/CWE-862, GHSA-22jm-h49p-29qw). 1.32.0 records the session on createTask, answers another session's lookup, result read, status update or cancel as a task not found, pages listTasks per session, and checks a request's related task against its session before queueing anything for it (modelcontextprotocol/typescript-sdk#2925). Only an HTTP server that passes taskStore is exposed; the 2.x packages (@modelcontextprotocol/server, client and core) are not affected. Experimental tasks are deprecated: the 2026-07-28 specification replaced them with a redesigned extension.
How to fix
Upgrade @modelcontextprotocol/sdk to 1.32.0 or later and pin it. If you cannot upgrade yet, stop passing taskStore, or create one InMemoryTaskStore per session. Experimental tasks are deprecated in favour of the 2026-07-28 specification's redesigned extension, so plan to leave them.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-TSSDK-CVE-2026-111767-001
Limitations
Reports @modelcontextprotocol/sdk from 1.24.0 up to 1.32.0 where a package.json, lockfile or MCP config states the version, reporting a range that admits an affected version. latest was 1.32.1 on 2026-10-21 and states no version, so it is not reported. It reads the version, not whether a server passes taskStore, so a server or client on an affected version that never uses experimental tasks is reported without being exposed; the advisory's own test is that grep -ri taskstore outside node_modules finds nothing. 1.23.1, published after 1.24.0, ships no task store and is not reported, and the 2.x packages are not read. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.
References
- CVE: CVE-2026-111767
- OWASP MCP Top 10: MCP07:2025 (Insufficient Authentication & Authorization), MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering)
- OWASP Agentic Top 10: ASI03 (Identity and Privilege Abuse), ASI04 (Agentic Supply Chain Vulnerabilities)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-SUPPLY-08 (MCP-Specific Vuln)
- CSA AI Controls Matrix (AICM): IAM-01, STA-08
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-TSSDK-CVE-2026-111767-001.md: the page then shows that text, with the registry reference appended under it.