CVE-2026-111768: MCP TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation
High CVSS 7.5
- OSV id
- GHSA-46jr-4wx8-v453
- Also known as
- CVE-2026-111768
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| @modelcontextprotocol/sdk npm |
>= 1.3.0, < 1.32.0 | 1.32.0 |
| @modelcontextprotocol/server npm |
>= 2.0.0, < 2.3.0 | 2.3.0 |
Versions we track that it affects: @modelcontextprotocol/sdk 1.30.0;
How to fix it
@modelcontextprotocol/sdk (npm)
Upgrade @modelcontextprotocol/sdk to 1.32.0 or later.
npm install @modelcontextprotocol/sdk@1.32.0
# if it is an indirect dependency: npm update @modelcontextprotocol/sdk (or npm audit fix)
- If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
@modelcontextprotocol/server (npm)
Upgrade @modelcontextprotocol/server to 2.3.0 or later.
npm install @modelcontextprotocol/server@2.3.0
# if it is an indirect dependency: npm update @modelcontextprotocol/server (or npm audit fix)
- If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
Summary
In affected versions, servers put no limit on how many array elements and object keys they validated in one request. One HTTP request within the default 4 MiB size limit could exhaust the server's memory, and the process aborted with JavaScript heap out of memory.
No credentials are needed, unless you authenticate requests before they reach the SDK.
Am I affected?
Yes, if clients you do not fully trust can reach your server over HTTP. The risk is highest for McpServer tools whose input contains an array or a record. stdio-only servers are not affected.
Affected versions:
@modelcontextprotocol/sdk1.3.0 through 1.31.0@modelcontextprotocol/server2.0.0 through 2.2.0
Fix
Upgrade to:
- 1.x:
@modelcontextprotocol/sdk1.32.0 or later - 2.x:
@modelcontextprotocol/server2.3.0 or later
Upgrading alone changes nothing. The patched versions add an McpServer option, maxToolInputElements, that is off by default. Make both of these changes:
- Set
maxToolInputElementsjust above the largest input your tools need, for examplenew McpServer(info, { maxToolInputElements: 10_000 }). It counts array elements and object keys in a call's arguments. A call over the limit gets anisError: trueresult. - Lower the request size limit to what your tools need. The option covers tool arguments only, and the size limit covers everything else. Set
maxRequestBodySizeon the transport orcreateMcpHandler(). If you parse the body yourself, for example withexpress.json()or Fastify, set that parser's limit.
If you cannot upgrade yet, make the second change. maxRequestBodySize needs @modelcontextprotocol/sdk 1.30.1 or @modelcontextprotocol/server 2.1.0. Below that, use a reverse proxy.
References
- GHSA-46jr-4wx8-v453 on OSV.dev
- Web: https://github.com/modelcontextprotocol/typescript-sdk/security/advisories/GHSA-46jr-4wx8-v453
- Web: https://github.com/modelcontextprotocol/typescript-sdk/pull/2926
- Web: https://github.com/modelcontextprotocol/typescript-sdk/pull/2927
- Web: https://github.com/modelcontextprotocol/typescript-sdk/commit/6d8dbc6cb590edf766fcb66b636ca6b654e99c37
- Web: https://github.com/modelcontextprotocol/typescript-sdk/commit/fd26801b3b387742fe24a90ed4b275dd6072209f
- Package: https://github.com/modelcontextprotocol/typescript-sdk
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.