Description
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.
Published: 2026-11-05
Score: 7.5 High
EPSS: n/a
KEV: No
Impact: Denial of Service
Action: Immediate Patch
AI Analysis

Impact

The Model Context Protocol TypeScript SDK allowed servers to validate HTTP requests containing arrays or object keys without imposing limits on the number of elements or keys. A single request within the default 4 MiB payload size can force the JavaScript heap to exhaust, terminating the server process. The vulnerability does not require special credentials unless the application authenticates before SDK processing; an unauthenticated HTTP request is sufficient to trigger the failure. The memory exhaustion is the defining impact, resulting in a denial‑of‑service of the affected service.

Affected Systems

Affected products include the Model Context Protocol SDK for JavaScript from versions 1.3.0 through 1.32.0, the Model Context Protocol Server from versions 2.0.0 through 2.3.0, and the TypeScript SDK interface used by developers. These versions lack validation bounds on array elements and object keys, enabling large workloads within the normal request size limit.

Risk and Exploitability

The CVSS score of 7.5 classifies this as a high‑severity vulnerability, and although an EPSS score is not provided, the lack of mitigation until configuration changes implies a real risk of exploitation. The issue is not listed in the CISA KEV catalog, but attackers could abuse public HTTP endpoints to send crafted large arrays or objects, potentially exhausting server memory and causing availability outages. The vulnerability can be leveraged remotely via standard HTTP requests, making it broadly exploitable in any exposed service that uses the SDK without additional bounds.

Generated by OpenCVE AI on November 5, 2026 at 22:20 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update @modelcontextprotocol/sdk to version 1.32.0 or later, and @modelcontextprotocol/server to version 2.3.0 or later, to install the fixed validation logic.
  • Configure a tool‑input element bound in the SDK or server configuration to limit the number of array elements or object keys processed per request.
  • Set an appropriate request body size limit on the HTTP server, ensuring that the maximum size is below or equal to the cleaned 4 MiB limit to prevent large payloads from triggering memory exhaustion.

Generated by OpenCVE AI on November 5, 2026 at 22:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-46jr-4wx8-v453 MCP TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation
History

Thu, 05 Nov 2026 21:30:00 +0000

Type Values Removed Values Added
Description 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.
Title Model Context Protocol TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation
Weaknesses CWE-770
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-11-05T21:22:44.119Z

Reserved: 2026-10-16T17:52:09.082Z

Link: CVE-2026-111768

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-05T22:17:45.457

Modified: 2026-11-05T22:17:45.457

Link: CVE-2026-111768

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-05T22:30:17Z

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling