AI Stack Alert High For AppSec, AI Eng, SOC / IR, CISO AI-assisted
MCP TypeScript SDK HTTP transports lacked body size and JSON-RPC batch limits (GHSA-f897-62hf-6gxq)
Affected versions of the MCP TypeScript SDK's HTTP server transports and handlers did not limit POST body size or the number of messages in a JSON-RPC batch. Large requests could exhaust server memory, and a long batch could block other clients. Fixed in @modelcontextprotocol/sdk 1.30.1, server 2.1.0, node 2.1.0, and hono 2.0.1.
Why it matters
Any MCP server reachable over Streamable HTTP by untrusted clients can be driven to memory exhaustion or denial of service without credentials, unless requests are authenticated before reaching the SDK. Stdio-only servers are not affected.
Do this
- Identify all MCP servers using Streamable HTTP and check installed @modelcontextprotocol/sdk, server, node, and hono versions.
- Upgrade @modelcontextprotocol/sdk to 1.30.1 or later on the 1.x line, or upgrade @modelcontextprotocol/server and @modelcontextprotocol/node to 2.1.0 and @modelcontextprotocol/hono to 2.0.1 or later. Upgrade every package installed.
- After upgrading, test clients that send bodies over 4 MiB or batches over 100 messages; raise the maxRequestBodySize option if needed.
- If upgrade is not possible, cap request body size at a reverse proxy in front of the MCP endpoint.
- Do not rely on express.json() for protection; it does not limit JSON-RPC batch length.
Signals
- NoCISA KEV
- 7.5CVSS
- 37/100Priority
- 90%Confidence
Evidence
“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.”
“If you cannot upgrade yet, cap request body size in a reverse proxy.”
Sources
Affected / related
@modelcontextprotocol/sdk, @modelcontextprotocol/server, @modelcontextprotocol/node, @modelcontextprotocol/hono
Published 2026-10-27 19:02 UTC · updated 2026-11-08 02:39 UTC · AI-assisted summary, checked against quoted sources · How we score