UTC
High

MCP TypeScript SDK: HTTP server transports and handlers did not limit request body size or JSON-RPC batch length

GHSA-f897-62hf-6gxq · published 2026-10-27

Severity
High
CVSS score
7.5
Chance of exploitation (EPSS)
No CVE
Fixed in
2.0.1
What it is

In affected versions, MCP servers reachable over HTTP put no limit on the size of a POST body or on the number of messages in a JSON-RPC batch. Large requests could exhaust the server's memory, and one long batch could block it from serving anyone else. No credentials were needed, unless your application authenticates requests before they reach the SDK.

What to do

Upgrade @modelcontextprotocol/hono to 2.0.1 or later, and @modelcontextprotocol/node to 2.1.0 or later, and @modelcontextprotocol/sdk to 1.30.1 or later, and @modelcontextprotocol/server to 2.1.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Upgrade to: 1.x: @modelcontextprotocol/sdk 1.30.1 or later 2.x: @modelcontextprotocol/server 2.1.0, @modelcontextprotocol/node 2.1.0 and @modelcontextprotocol/hono 2.0.1 or later. Upgrade every one you have installed. Bodies over 4 MiB now get 413, and batches over 100 messages get 400. If your clients send larger bodies, raise the new maxRequestBodySize option. If you cannot upgrade yet, cap request body size in a reverse proxy.

Affected
PackageRegistryAffectedFixed in
@modelcontextprotocol/hononpm>= 2.0.0, < 2.0.12.0.1
@modelcontextprotocol/nodenpm>= 2.0.0, < 2.1.02.1.0
@modelcontextprotocol/sdknpm>= 1.10.0, < 1.30.11.30.1
@modelcontextprotocol/servernpm>= 2.0.0, < 2.1.02.1.0
Downstream in the Official MCP Registry

401 registered MCP servers install an affected version today, by the dependency versions a fresh install resolves.

  • ai.ankimcp/anki-mcp-server@modelcontextprotocol/node@2.0.0
  • ai.makerportal/compute@modelcontextprotocol/sdk@1.30.0
  • ai.mentu/navigator@modelcontextprotocol/sdk@1.29.0
  • ai.myspaice/spaces@modelcontextprotocol/sdk@1.29.0
  • ai.sanctuaryprotocol/sanctuary@modelcontextprotocol/sdk@1.30.0
  • ai.sendshort/sendshort@modelcontextprotocol/sdk@1.30.0
  • ai.taasky/common-ground@modelcontextprotocol/server@2.0.0
  • app.somiya/mcp@modelcontextprotocol/sdk@1.30.0
  • cash.gage/gage@modelcontextprotocol/server@2.0.0
  • cloud.agkit/agkit@modelcontextprotocol/server@2.0.0
  • cn.housingsentinel/housing-sentinel@modelcontextprotocol/sdk@1.29.0
  • com.50heads/mcp@modelcontextprotocol/server@2.0.0
All 401 servers on the trace →

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].