CVE-2026-111767: MCP TypeScript SDK: Experimental tasks were not tied to the session that created them in npm Package @modelcontextprotocol/
A high-severity advisory for the npm package @modelcontextprotocol/sdk is fixed in version 1.32.0.
Key points
- @modelcontextprotocol/sdk (npm) has a high flaw.
- Tracked as CVE-2026-111767.
- Version 1.32.0.
Maintainers of @modelcontextprotocol/sdk, a package in the npm ecosystem, have published a high-severity security advisory (CVE-2026-111767): MCP TypeScript SDK: Experimental tasks were not tied to the session that created them.
At a glance
- Advisory
- GHSA-22jm-h49p-29qw
- CVE
- CVE-2026-111767
- Package
- @modelcontextprotocol/sdk (npm)
- Severity
- High
- Patched in
- 1.32.0
What is the issue?
The GitHub-reviewed advisory explains: 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
Affected versions
| Ecosystem | Package | Vulnerable | Patched |
|---|---|---|---|
| npm | @modelcontextprotocol/sdk | >= 1.24.0, < 1.32.0 | 1.32.0 |
The advisory lists a CVSS score of 8.6.
How to fix it
- Upgrade the affected package to the first patched version listed above.
- Rebuild and redeploy applications that bundle the vulnerable dependency.
- Run your dependency scanner (npm audit, pip-audit, Dependabot) to find transitive uses.
- Review the advisory references for workaround details if you cannot upgrade yet.
What to do and how to stay safe: CVE-2026-111767
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-111767?
CVE-2026-111767 is a security vulnerability in @modelcontextprotocol/sdk (npm).
Which version fixes CVE-2026-111767?
The fix is in version 1.32.0.
