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
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.
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.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @modelcontextprotocol/hono | npm | >= 2.0.0, < 2.0.1 | 2.0.1 |
| @modelcontextprotocol/node | npm | >= 2.0.0, < 2.1.0 | 2.1.0 |
| @modelcontextprotocol/sdk | npm | >= 1.10.0, < 1.30.1 | 1.30.1 |
| @modelcontextprotocol/server | npm | >= 2.0.0, < 2.1.0 | 2.1.0 |
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
- HightsParticles: Unbounded HTTP Request Body Buffering in @tsparticles/mcp-server Leads to Remote DoS@tsparticles/mcp-server
- HighMissing request-wide media budget allows single-request frontend resource exhaustionvllm
- HighvLLM : DoS via unvalidated mm_processor_kwargs in multimodal image processors (Isaac, InternVL, H2OVL, etc.)vllm
- HighFrame-count cap bypass in VideoMediaIO.load_base64 for video/jpeg via media_io_kwargs.video.num_framesvllm
- HighNemotron-VL processors disable Pillow decompression-bomb guard globally, enabling unauthenticated DoSvllm
- HighCross-tenant DoS via uninitialized LogprobsTensors with prompt_logprobsvllm
- HighMCP TypeScript SDK: Experimental tasks were not tied to the session that created them@modelcontextprotocol/sdk
- HighMCP TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation@modelcontextprotocol/sdk, @modelcontextprotocol/server
- HighMCP TypeScript server SDK: Shared transport or server instances delivered one HTTP client's messages to another@modelcontextprotocol/server
- HighMCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server@modelcontextprotocol/client, @modelcontextprotocol/sdk
- High@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse@modelcontextprotocol/sdk
- HighAnthropic's MCP TypeScript SDK has a ReDoS vulnerability@modelcontextprotocol/sdk
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.