# CVE-2026-111767: MCP TypeScript SDK: Experimental tasks were not tied to the session that created them


- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** CLSA-2026-1793097252, CLSA-2026-1793102531, ECHO-9411-00b8-28d5, GHSA-22jm-h49p-29qw, MINI-xh2p-cwp5-5g43, ROOT-APP-NPM-CVE-2026-111767

## What is CVE-2026-111767?

CVE-2026-111767 is a high-severity vulnerability in modelcontextprotocol typescript-sdk, published on 20 Oct 2026. 

### Official description

MCP TypeScript SDK is the official TypeScript SDK for Model Context Protocol servers and clients. From version 1.24.0 to before version 1.32.0, 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. This issue has been patched in version 1.32.0.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-111767?

2 open source packages ship an affected version, including @modelcontextprotocol/sdk.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@modelcontextprotocol/sdk` | npm | From 1.24.0 | 1.32.0 |
| `@modelcontextprotocol/sdk` | npm | From 1.24.0 | 1.32.0 |

## How do I fix CVE-2026-111767?

Upgrade @modelcontextprotocol/sdk to 1.32.0 or later.

## Is CVE-2026-111767 being exploited?

There is no known exploitation of CVE-2026-111767 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111767 and fix it if it is affected.

What it is: CVE-2026-111767 is a high-severity vulnerability in modelcontextprotocol typescript-sdk, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-111767 in the wild and no public exploit code.

Affected packages and fixed versions:
- @modelcontextprotocol/sdk (npm): affected from 1.24.0; fixed in 1.32.0
- @modelcontextprotocol/sdk (npm): affected from 1.24.0; fixed in 1.32.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-111767/ (Markdown: https://insights.sbomify.com/CVE-2026-111767/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111767
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111767
- OSV: https://osv.dev/vulnerability/CVE-2026-111767

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111767/
Summaries are generated and may contain mistakes; the official description above is the record.