Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
CVE-2025-66414 · GHSA-w48q-cv73-mx4w · published 2025-12-02 · updated 2026-02-17
- Severity
- High
- CVSS score
- 7.6
- Chance of exploitation (EPSS)
- 0.54%
- Fixed in
- 1.24.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Total
- CISA SSVC
The Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default for HTTP-based servers. When an HTTP-based MCP server is run on localhost without authentication with StreamableHTTPServerTransport or SSEServerTransport and has not enabled enableDnsRebindingProtection, a malicious website could exploit DNS rebinding to bypass same-origin policy restrictions and send requests to the local MCP server. This could allow an attacker to invoke tools or access resources exposed by the MCP server on behalf of the user in those limited circumstances.
Upgrade @modelcontextprotocol/sdk to 1.24.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @modelcontextprotocol/sdk | npm | < 1.24.0 | 1.24.0 |
116 registered MCP servers install an affected version today, by the dependency versions a fresh install resolves.
- ai.pixeldojo/mcp@modelcontextprotocol/sdk@1.4.1
- ai.wild-card/deepcontext@modelcontextprotocol/sdk@0.6.1
- com.kekwanu/syncline-mcp-server@modelcontextprotocol/sdk@0.5.0
- com.monikaskorykow/workshops@modelcontextprotocol/sdk@1.23.0
- dev.ezstat/ezstat-mcp-server@modelcontextprotocol/sdk@1.13.2
- io.github.aabxtract/koda@modelcontextprotocol/sdk@1.0.4
- io.github.AaronVick/echorift-mcp@modelcontextprotocol/sdk@0.5.0
- io.github.agent-idx/mcp@modelcontextprotocol/sdk@0.6.1
- io.github.AINative-Studio/ainative-browser-mcp@modelcontextprotocol/sdk@0.5.0
- io.github.alicelabs-llc/marketnow@modelcontextprotocol/sdk@0.5.0
- io.github.alvinjchoi/gtasks-mcp@modelcontextprotocol/sdk@1.0.1
- io.github.anyproto/anytype-mcp@modelcontextprotocol/sdk@1.18.0
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- HighMCP TypeScript SDK: HTTP server transports and handlers did not limit request body size or JSON-RPC batch length@modelcontextprotocol/hono, @modelcontextprotocol/node, @modelcontextprotocol/sdk, @modelcontextprotocol/server
- HighMCP TypeScript SDK: Experimental tasks were not tied to the session that created them@modelcontextprotocol/sdk
- HighMCP TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation@modelcontextprotocol/sdk, @modelcontextprotocol/server
- HighMCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server@modelcontextprotocol/client, @modelcontextprotocol/sdk
- High@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse@modelcontextprotocol/sdk
- HighAnthropic's MCP TypeScript SDK has a ReDoS vulnerability@modelcontextprotocol/sdk
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.