@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
CVE-2026-25536 · GHSA-345p-7cg4-v4c7 · published 2026-02-04 · updated 2026-02-09
- Severity
- High
- CVSS score
- 7.1
- Chance of exploitation (EPSS)
- 0.29%
- Fixed in
- 1.26.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
This advisory covers two related but distinct vulnerabilities. A deployment may be affected by one or both.
Upgrade @modelcontextprotocol/sdk to 1.26.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.
The fix (v1.26.0) adds runtime guards that turn silent data misrouting into immediate, actionable errors: 1. Protocol.connect() now throws if the protocol is already connected to a transport, preventing silent transport overwriting (addresses Issue 2) 2. Stateless now throws if called more than once, enforcing one-request-per-transport in stateless mode (addresses Issue 1) 3. In-flight request handler abort controllers are cleaned up on close(), and sendNotification/sendRequest in handler extras check the abort signal before sending, preventing messages from leaking after a transport is replaced Servers that were incorrectly reusing instances will now receive a clear error message directing…
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @modelcontextprotocol/sdk | npm | >= 1.10.0, <= 1.25.3 | 1.26.0 |
51 registered MCP servers install an affected version today, by the dependency versions a fresh install resolves.
- com.apideck/mcp@modelcontextprotocol/sdk@1.25.2
- com.docfork/docfork-mcp@modelcontextprotocol/sdk@1.25.2
- com.monikaskorykow/workshops@modelcontextprotocol/sdk@1.23.0
- dev.ezstat/ezstat-mcp-server@modelcontextprotocol/sdk@1.13.2
- io.github.anyproto/anytype-mcp@modelcontextprotocol/sdk@1.18.0
- io.github.askman-dev/agent-never-give-up@modelcontextprotocol/sdk@1.23.0
- io.github.AungMyoKyaw/betterprompt-mcp@modelcontextprotocol/sdk@1.18.0
- io.github.BamaCharanChhandogi/blogcaster-mcp@modelcontextprotocol/sdk@1.20.2
- io.github.brightdata/brightdata-mcp@modelcontextprotocol/sdk@1.21.2
- io.github.bytedance/mcp-server-browser@modelcontextprotocol/sdk@1.15.1
- io.github.bytedance/mcp-server-commands@modelcontextprotocol/sdk@1.15.1
- io.github.bytedance/mcp-server-filesystem@modelcontextprotocol/sdk@1.15.1
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- 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
- 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 SDK: OAuth client could send credentials to an authorization server chosen by the MCP server@modelcontextprotocol/client, @modelcontextprotocol/sdk
- HighAnthropic's MCP TypeScript SDK has a ReDoS vulnerability@modelcontextprotocol/sdk
- HighModel Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default@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.