Answer in brief
CVE-2026-111768 records a High severity (CVSS 7.5) vulnerability in Model Context Protocol TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation. The current sources do not mark it as known exploited. The current feed maps @modelcontextprotocol/sdk (generic), @modelcontextprotocol/server (generic), modelcontextprotocol/typescript-sdk (generic), @modelcontextprotocol/sdk (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps @modelcontextprotocol/sdk (generic), @modelcontextprotocol/server (generic), modelcontextprotocol/typescript-sdk (generic), @modelcontextprotocol/sdk (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| @modelcontextprotocol/sdkgeneric | >=1.3.0 <1.32.0 | 1.32.0 |
| @modelcontextprotocol/servergeneric | >=2.0.0 <2.3.0 | 2.3.0 |
| modelcontextprotocol/typescript-sdkgeneric | >=1.3.0 <1.32.0 | 1.32.0 |
| @modelcontextprotocol/sdknpm | >=1.3.0,<1.32.0 | 1.32.0 |
| @modelcontextprotocol/servernpm | >=2.0.0,<2.3.0 | 2.3.0 |
Published upstream
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 20, 2026
The Model Context Protocol TypeScript SDK provides TypeScript client and server implementations of the Model Context Protocol. From 1.3.0 until 1.32.0 in @modelcontextprotocol/sdk and from 2.0.0 until 2.3.0 in @modelcontextprotocol/server, HTTP servers did not enforce a limit on the number of array elements and object keys validated in one request. The affected surface is validation of HTTP requests containing arrays or object keys. The trigger is an array-element or object-key validation workload large enough to exhaust memory while remaining within the request size limit. A single request within the default 4 MiB limit can terminate the process with JavaScript heap exhaustion. No credentials are required unless the application authenticates before SDK processing. Tools accepting arrays or records carry the greatest risk. stdio-only servers do not expose the HTTP request path. Upgrading alone does not enable the new validation bound. Operators must configure both a tool-input element bound and an appropriate request body size limit. This issue is fixed in @modelcontextprotocol/sdk 1.32.0 and @modelcontextprotocol/server 2.3.0.
Quoted source text, attributed separately from HOL analysis.