CVE-2026-111768: @modelcontextprotocol server · Unthrottled Resource Allocation
Affects @modelcontextprotocol serverSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 2.3.0 soon.
Data as of 5 Nov 2026, 21:34 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 1.32.0, 2.3.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade server to 2.3.0; typescript-sdk and sdk to 1.32.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| modelcontextprotocoltypescript-sdk | Affected
| Fixed in
|
| @modelcontextprotocolserver | Affected
| Fixed in
|
| @modelcontextprotocolsdk | Affected
| Fixed in
|
AI-suggested
Upgrade to @modelcontextprotocol/sdk version 1.32.0 or later and @modelcontextprotocol/server version 2.3.0 or later to obtain the fix. Additionally, operators must configure both a tool-input element bound to limit the number of array elements or object keys validated per request and set an appropriate request body size limit to prevent memory exhaustion. Simply upgrading without configuring these limits does not fully mitigate the vulnerability.
Description
CVE-2026-111768 is a high-severity vulnerability in the @modelcontextprotocol TypeScript SDK and server components. Versions from 1.3.0 up to but not including 1.32.0 of the SDK, and 2.0.0 up to but not including 2.3.0 of the server, do not enforce limits on the number of array elements or object keys validated in a single HTTP request. This can lead to JavaScript heap exhaustion and process termination when processing large arrays or objects within the default 4 MiB request size limit. The vulnerability is fixed in versions 1.32.0 of the SDK and 2.3.0 of the server. Operators must configure both input element bounds and request body size limits to fully mitigate the issue.
References
- github.com/modelcontextprotocol/typescript-sdk/security/advisories/GHSA-46jr-4wx8-v453 (opens in a new tab)
- github.com/modelcontextprotocol/typescript-sdk/pull/2926 (opens in a new tab)
- github.com/modelcontextprotocol/typescript-sdk/pull/2927 (opens in a new tab)
- github.com/modelcontextprotocol/typescript-sdk/commit/6d8dbc6cb590edf766fcb66b636ca6b654e99c37 (opens in a new tab)
- github.com/modelcontextprotocol/typescript-sdk/commit/fd26801b3b387742fe24a90ed4b275dd6072209f (opens in a new tab)
- github.com/modelcontextprotocol/typescript-sdk/releases/tag/1.32.0 (opens in a new tab)
- github.com/modelcontextprotocol/typescript-sdk/releases/tag/@modelcontextprotocol/server@2.3.0 (opens in a new tab)