INCIDENT MAP

Browse / MCP and Tool Server Flaws / GHSA-f897-62hf-6gxq

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

GHSA-f897-62hf-6gxq ยท 2026-10-27 high

Class
MCP and Tool Server Flaws (filed by a model that read the advisory)
Technique
Denial of service
Affected
@modelcontextprotocol/sdk (npm)
CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

How it works, in short

MCP HTTP servers accept unbounded POST bodies and JSON-RPC batches, so oversized requests exhaust memory and block other clients. (Our summary, written by a model. The source text is below.)

Details

Summary

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.

Am I affected?

Yes, if clients you do not fully trust can reach your server over Streamable HTTP. A body parser such as express.json() does not protect you, because it does not limit batch length. Servers that only use stdio are not affected.

Affected versions:

Fix

Upgrade to:

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.

References

Source: GitHub Advisory Database, used under CC BY 4.0.