UTC
High

Model Context Protocol (MCP) Python SDK does not enable DNS rebinding protection by default

CVE-2025-66416 · GHSA-9h52-p55h-vw2f · published 2025-12-02 · updated 2026-07-16

Severity
High
CVSS score
7.6
Chance of exploitation (EPSS)
0.54%
Fixed in
1.23.0
  • Exploitation No known exploitation
  • Automatable No
  • Technical impact Total
  • CISA SSVC
What it is

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.

What to do

Upgrade mcp to 1.23.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.

Affected
PackageRegistryAffectedFixed in
mcpPyPI< 1.23.01.23.0
Downstream in the Official MCP Registry

9 registered MCP servers install an affected version today, by the dependency versions a fresh install resolves.

  • com.cyberspf/mcpmcp@1.9.4
  • io.github.abhichandra21/promptheusmcp@1.12.4
  • io.github.AdonaiVera/fiftyone-mcp-servermcp@0.9.1
  • io.github.AndreySukhanov/summarix-telegrammcp@1.12.4
  • io.github.cr7258/elasticsearch-mcp-servermcp@1.9.2
  • io.github.domdomegg/time-mcp-pypimcp@1.13.1
  • io.github.kushknows/weather-mcp-servermcp@1.13.1
  • io.github.sellisd/mcp-unitsmcp@1.15.0
  • io.github.thomasxm/crowdsentinel-mcp-servermcp@1.9.2
See the trace →

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].