MCP TypeScript shared transport sends responses to the wrong client
Reusing an HTTP server or transport across clients allows overlapping request identifiers to associate a response with the wrong connection. Applications must isolate server and transport state per request or session.
Reusing an HTTP server or transport across clients allows overlapping request identifiers to associate a response with the wrong connection. Applications must isolate server and transport state per request or session.
This is a maintainer-documented vulnerability disclosure, not evidence of exploitation against a named customer. Affected ranges: @modelcontextprotocol/server >= 2.0.0, < 2.3.0. The maintainer lists patched releases: @modelcontextprotocol/server 2.3.0.
Takeaway
Check the deployed package and its configuration against the advisory. Apply the listed fix on a supported release line and verify the trust boundary with an untrusted client or repository.