{"description":"Trending threats, MITRE ATT\u0026CK coverage, and detection metadata. Fed continuously.","favicon":"https://feed.craftedsignal.io/favicon-32x32.png","feed_url":"https://feed.craftedsignal.io/products/@modelcontextprotocol/server-2.0.0-2.2.0/feed.json","home_page_url":"https://feed.craftedsignal.io/","icon":"https://feed.craftedsignal.io/apple-touch-icon.png","items":[{"_cs_actors":[],"_cs_cpes":[],"_cs_cves":[{"id":"CVE-2026-111768"}],"_cs_exploited":false,"_cs_has_poc":false,"_cs_poc_references":[],"_cs_products":["@modelcontextprotocol/sdk (1.3.0-1.31.0)","@modelcontextprotocol/server (2.0.0-2.2.0)"],"_cs_severities":["medium"],"_cs_tags":[],"_cs_type":"advisory","_cs_vendors":["Model Context Protocol"],"content_html":"\u003cp\u003eThe Model Context Protocol (MCP) TypeScript SDK, specifically the \u003ccode\u003e@modelcontextprotocol/sdk\u003c/code\u003e (versions 1.3.0 to 1.31.0) and \u003ccode\u003e@modelcontextprotocol/server\u003c/code\u003e (versions 2.0.0 to 2.2.0) packages, contains a memory exhaustion vulnerability (CVE-2026-111768). The SDK fails to impose validation limits on the number of array elements and object keys processed during an incoming HTTP request. An attacker can craft an HTTP request that stays within the default 4 MiB size limit but contains a highly complex or deeply nested structure, forcing the server to consume excessive memory during parsing. This results in a JavaScript heap out of memory error, causing the MCP server process to crash. This vulnerability is primarily exploitable in environments where the MCP server is exposed via HTTP to untrusted clients, such as tools configured using \u003ccode\u003eMcpServer\u003c/code\u003e.\u003c/p\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation results in a denial-of-service (DoS) condition, rendering the affected MCP server process unavailable. This impacts applications and services relying on MCP servers for tool execution and data exchange. Infrastructure utilizing internet-facing MCP servers is at the highest risk, as the vulnerability does not require authentication unless implemented manually before the request reaches the SDK.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eUpgrade to the patched versions immediately: \u003ccode\u003e@modelcontextprotocol/sdk\u003c/code\u003e to 1.32.0 or later, and \u003ccode\u003e@modelcontextprotocol/server\u003c/code\u003e to 2.3.0 or later.\u003c/li\u003e\n\u003cli\u003eImplement the \u003ccode\u003emaxToolInputElements\u003c/code\u003e option when initializing \u003ccode\u003eMcpServer\u003c/code\u003e to limit the number of elements and keys in tool arguments.\u003c/li\u003e\n\u003cli\u003eRestrict request sizes by configuring \u003ccode\u003emaxRequestBodySize\u003c/code\u003e on the transport or \u003ccode\u003ecreateMcpHandler()\u003c/code\u003e, or by setting limits on front-end reverse proxies or body parsers (e.g., Express or Fastify) if the SDK upgrade is not immediately possible.\u003c/li\u003e\n\u003cli\u003eAudit network exposures for all MCP-based services to ensure they are not unnecessarily exposed to untrusted internet traffic.\u003c/li\u003e\n\u003c/ol\u003e\n","date_modified":"2026-10-20T23:55:43Z","date_published":"2026-10-20T23:55:43Z","id":"https://feed.craftedsignal.io/briefs/2026-10-mcp-typescript-sdk-dos/","summary":"The Model Context Protocol (MCP) TypeScript SDK is vulnerable to a denial-of-service condition where unauthenticated HTTP requests can exhaust server memory by bypassing array element and object key validation limits.","title":"Model Context Protocol TypeScript SDK: Memory exhaustion via array and object validation (CVE-2026-111768)","url":"https://feed.craftedsignal.io/briefs/2026-10-mcp-typescript-sdk-dos/"}],"language":"en","title":"CraftedSignal Threat Feed - @Modelcontextprotocol/Server (2.0.0-2.2.0)","version":"https://jsonfeed.org/version/1.1"}