Products / @modelcontextprotocol/sdk
@modelcontextprotocol/sdk
9 records.
- MCP TypeScript SDK: HTTP server transports and handlers did not limit request body size or JSON-RPC batch length MCP HTTP servers accept unbounded POST bodies and JSON-RPC batches, so oversized requests exhaust memory and block other clients.
- MCP TypeScript SDK: Experimental tasks were not tied to the session that created them The MCP TypeScript SDK's experimental task store did not tie tasks to their creating session, letting other clients list, read and cancel them.
- MCP TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation The MCP TypeScript SDK validates unlimited array elements and object keys, so one HTTP request within the size limit exhausts server memory.
- MCP TypeScript client SDK: HTTP client transports and OAuth requests followed cross-origin redirects and re-sent custom headers and request bodies Cross-origin redirects cause the client to resend custom headers and request bodies, including OAuth secrets, to an attacker-chosen origin.
- MCP TypeScript SDK: Server bearer authentication accepted tokens issued for another service
- MCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server A malicious MCP server can choose its own authorization server, so the client automatically sends stored refresh tokens and client secrets to it.
- @modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse Reusing one transport across clients makes colliding JSON-RPC IDs route responses to the wrong client's stream.
- Anthropic's MCP TypeScript SDK has a ReDoS vulnerability Crafted URIs matched against exploded resource template patterns trigger catastrophic regex backtracking in the MCP SDK URI template matcher, hanging the server.
- Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default