@Modelcontextprotocol/Server (>= 2.0.0, < 2.3.0) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/@modelcontextprotocol/server--2.0.0--2.3.0/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 20 Oct 2026 23:55:37 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgModel Context Protocol TypeScript SDK: Cross-client message leakage (CVE-2026-111770)https://feed.craftedsignal.io/briefs/2026-10-mcp-sdk-message-leak/Tue, 20 Oct 2026 23:55:37 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-mcp-sdk-message-leak/A high-severity vulnerability in the MCP TypeScript SDK (CVE-2026-111770) allows an MCP server to misroute messages between clients due to JSON-RPC request ID collisions when server instances are incorrectly shared.The MCP TypeScript SDK is vulnerable to cross-client message leakage when implemented as a shared, stateless instance. Because the protocol identifies messages by JSON-RPC IDs, which typically reset at 0 for every client, concurrent requests reaching a shared McpServer or transport instance result in ID collisions. In this state, an MCP server may erroneously return one client's responses or push notifications to another client sharing the same instance. This behavior was unintentionally encouraged by early SDK documentation, which provided examples using globally initialized server instances in common Node.js frameworks like Hono, Express, and Fastify. The vulnerability affects @modelcontextprotocol/server versions 2.0.0 through 2.2.0. Successful exploitation allows for sensitive information disclosure between authorized clients interacting with the same MCP server instance.

Impact

Successful exploitation results in unauthorized data access where clients receive responses or notifications intended for other users. This impacts any multi-user environment where a single MCP server is exposed via HTTP and initialized as a singleton. Organizations relying on this SDK for integrating LLM tools or internal automation are at risk of cross-session data leakage.

Recommendation

  1. Upgrade the @modelcontextprotocol/server package to version 2.3.0 or later to ensure the SDK actively enforces connection isolation and rejects attempts to share instances.
  2. Audit all existing MCP server implementations for the singleton pattern; refactor code to instantiate McpServer and transport objects either per-request or per-session using a sessionIdGenerator.
  3. Validate implementation patterns against the official SDK update guidance to ensure session-specific state management is strictly applied.
]]>highadvisoryinformation-disclosuremcpsdk-vulnerability