CVE-2025-66416: DNS Rebinding Protection Disabled by Default in Model Context Protocol Python SDK for Servers Running on Localhost
### Description The Model Context Protocol (MCP) Python 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 using `FastMCP` with streamable HTTP or SSE transport, and has not configured `TransportSecuritySettings`, 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. Note that running HTTP-based MCP servers locally without authentication is not recommended per MCP security best practices. This issue does not affect servers using stdio transport. Servers created via `FastMCP()` now have DNS rebinding protection enabled by default when the `host` parameter is `127.0.0.1` or `localhost`. Users are advised to update to version `1.23.0` to receive this automatic protection. Users with custom low-level server configurations using `StreamableHTTPSessionManager` or `SseServerTransport` directly should explicitly configure `TransportSecuritySettings` when running an unauthenticated server on localhost.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-66416?
CVE-2025-66416 has a critical severity rating due to the potential for exploit via DNS rebinding.
How do I fix CVE-2025-66416?
To fix CVE-2025-66416, upgrade the MCP Python SDK to version 1.23.0 or later.
What systems are affected by CVE-2025-66416?
CVE-2025-66416 affects HTTP-based servers using the MCP Python SDK when running without authentication on localhost.
What is DNS rebinding in the context of CVE-2025-66416?
DNS rebinding is a method used by attackers to gain control over a user's browser and access restricted network services.
Is authentication necessary to mitigate CVE-2025-66416?
Yes, authentication is necessary to mitigate the risks associated with CVE-2025-66416 when using the MCP Python SDK.