CVE-2025-66416: modelcontextprotocol python-sdk · Insecure Default Initialization of Resource
Affects modelcontextprotocol python-sdkSource CVE Database V5
Not known to be exploited · CVSS 7.6 High : upgrade to 1.23.0 soon.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.23.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade mcp to 1.23.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPImcppkg:pypi/mcpOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately upgrade the MCP Python SDK to version 1.23.0 or later, where DNS rebinding protection is enabled by default. For environments where upgrading is not immediately feasible, administrators should explicitly configure TransportSecuritySettings to enable DNS rebinding protection and enforce authentication on all HTTP-based MCP servers. Avoid running MCP servers on localhost without authentication or transport security, especially in production or sensitive environments. Developers should consider switching to stdio transport for MCP servers where possible, as it is not affected by this vulnerability. Network-level mitigations include restricting outbound DNS queries and monitoring for suspicious DNS rebinding patterns. Security teams should educate users about the risks of visiting untrusted websites while running local MCP servers. Finally, incorporate MCP server security checks into CI/CD pipelines and vulnerability management programs to ensure compliance with best practices.
Description
### 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.