UTC
High

@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
What it is

This advisory covers two related but distinct vulnerabilities. A deployment may be affected by one or both.

What to do

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…

Affected
PackageRegistryAffectedFixed in
@modelcontextprotocol/sdknpm>= 1.10.0, <= 1.25.31.26.0
Downstream in the Official MCP Registry

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
All 51 servers on the trace →

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].