CVE-2026-25536: @modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
MCP TypeScript SDK is the official TypeScript SDK for Model Context Protocol servers and clients. From version 1.10.0 to 1.25.3, cross-client response data leak when a single McpServer/Server and transport instance is reused across multiple client connections, most commonly in stateless StreamableHTTPServerTransport deployments. This issue has been patched in version 1.26.0.
Security readout for executives and security teams
Plain-English summary
This flaw can cause an MCP service to send one client's response data to another client when server and transport objects are reused incorrectly. The main business risk is confidential data exposure between authenticated or otherwise permitted clients. The affected SDK range is 1.10.0 through 1.25.3, with a patch in 1.26.0.
Executive priority
Treat as high priority where MCP services process sensitive customer, employee, or operational data. Patch exposed or multi-tenant deployments first.
Technical view
@modelcontextprotocol/typescript-sdk versions >=1.10.0 and <1.26.0 have a cross-client response data leak tied to reuse of a single McpServer/Server and transport instance across connections, commonly stateless StreamableHTTPServerTransport. The CVSS 3.1 score is 7.1, driven by network access, low complexity, low privileges, high confidentiality impact, and low integrity impact.
Likely exposure
Exposure is most likely in MCP deployments using the TypeScript SDK, especially network-accessible stateless HTTP transports that reuse shared server or transport instances across multiple clients.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. The condition requires access as a client or low-privileged actor and a vulnerable deployment pattern.
Researcher notes
Evidence supports a concurrency or time-of-check/time-of-use class issue mapped to CWE-362 and CWE-367. The provided sources identify the vulnerable version range, common deployment pattern, and fixed version, but do not provide active exploitation evidence.
Mitigation direction
Upgrade @modelcontextprotocol/typescript-sdk to version 1.26.0 or later.
Inventory MCP services using TypeScript SDK versions 1.10.0 through 1.25.3.
Review stateless StreamableHTTPServerTransport deployments for shared server or transport instance reuse.
Apply Red Hat or vendor package advisories where consuming redistributed packages.
Monitor upstream advisory GHSA-345p-7cg4-v4c7 for any additional guidance.
Validation and detection
Check package manifests, lockfiles, containers, and SBOMs for affected SDK versions.
Confirm runtime deployments use @modelcontextprotocol/typescript-sdk 1.26.0 or later.
Inspect MCP server initialization for shared McpServer/Server and transport objects across clients.
Run regression tests covering concurrent client requests and response isolation.
Review logs or reports for unexplained cross-client response mismatches.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-362: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-362 · source CWE mapping
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.