MCP Python SDK: Unbounded Session Accumulation in StreamableHTTP Transport Enables Resource Exhaustion
CVE-2026-59951 · GHSA-84m7-p3x7-pcfv · published 2026-10-15
- Severity
- Medium
- CVSS score
- 7.5
- Chance of exploitation (EPSS)
- 0.46%
- Fixed in
- 2.2.0
- Exploitation No known exploitation
- Automatable Yes
- Technical impact Partial
- CISA SSVC
In affected versions, a Streamable HTTP server in stateful mode (the default) never reclaimed session state: sessions did not expire; a client DELETE ended the session but left its entry registered; a session whose first request was refused stayed registered with a running task. Each session also kept its parsed initialize parameters, and the number of sessions was unlimited. A client that could reach the endpoint could grow server memory without bound using ordinary short requests; only a restart reclaimed it.
Upgrade mcp to 2.2.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 mcp 1.30.0 (1.x) or 2.2.0 (2.x) or later. In those versions: a session with no request in flight for sessionidletimeout seconds (default 1800) is closed and its ID then answers 404; open streams and in-progress requests keep it alive; at most maxsessions sessions exist at once (default 10000); a request that would open another is answered 503; a session is discarded as soon as it ends, whether by DELETE, expiry, or a refused opening request. Both settings are keyword arguments on FastMCP(...) (1.x), MCPServer.run() / streamablehttpapp() (2.x) and StreamableHTTPSessionManager; None disables them.
46 registered MCP servers install an affected version today, by the dependency versions a fresh install resolves.
- ai.datavidence/datavidence-financialsmcp@2.1.1
- ai.solwyn/solwynmcp@2.1.1
- com.browser-use/browser-usemcp@2.1.1
- com.cyberspf/mcpmcp@1.9.4
- com.lucidlink/mcpmcp@2.0.0
- com.nautaai/holster-mcpmcp@1.27.2
- io.github.abhichandra21/promptheusmcp@1.12.4
- io.github.Alejandrehl/kainext-binance-mcpmcp@1.29.0
- io.github.amin-ale/mcp-quickbooksmcp@1.28.1
- io.github.AndreySukhanov/summarix-telegrammcp@1.12.4
- io.github.AS-XS/ai-pensieve-mcpmcp@2.1.1
- io.github.ashlesh-t/cognirepomcp@1.27.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
- HighMCP TypeScript SDK: HTTP server transports and handlers did not limit request body size or JSON-RPC batch length@modelcontextprotocol/hono, @modelcontextprotocol/node, @modelcontextprotocol/sdk, @modelcontextprotocol/server
- HighvLLM : DoS via unvalidated mm_processor_kwargs in multimodal image processors (Isaac, InternVL, H2OVL, etc.)vllm
- HighMCP TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation@modelcontextprotocol/sdk, @modelcontextprotocol/server
- HighFrame-count cap bypass in VideoMediaIO.load_base64 for video/jpeg via media_io_kwargs.video.num_framesvllm
- HighModel Context Protocol Python SDK: OAuth client could send credentials to an authorization server chosen by the MCP servermcp, mcp
- HighHTTP server transports and OAuth endpoints read request bodies with no size limitmcp, mcp
- HighMCP Python SDK: Experimental task handlers allow any client to access and cancel other clients' tasksmcp
- HighMCP Python SDK: HTTP transports serve session requests without verifying the authenticated principalmcp
- HighMCP Python SDK: WebSocket server transport does not support Host/Origin validationmcp
- HighModel Context Protocol (MCP) Python SDK does not enable DNS rebinding protection by defaultmcp
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.