Quick answers
- Is CVE-2025-66416 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-66416 being exploited in the wild.
- How severe is CVE-2025-66416?
- High severity, with a CVSS score of 8.1, published 2 December 2025.
- Which products and versions are affected?
- Anthropic Model Context Protocol < 1.23.0; mcp (PyPI) ECOSYSTEM:introduced=0,fixed=1.23.0.
- Is there a fix for CVE-2025-66416?
- Yes. mcp (PyPI): upgrade to 1.23.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-66416 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-66416?
- Check whether you run Anthropic Model Context Protocol, Lfprojects Mcp Python Sdk or mcp (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- mcp (PyPI): upgrade to 1.23.0 or later
pip install "mcp>=1.23.0"
Technical details
The MCP Python SDK is vulnerable to DNS rebinding attacks because it lacks default protection for HTTP-based servers (specifically those using FastMCP with streamable HTTP or SSE transport). When a server is hosted on localhost without authentication or explicit TransportSecuritySettings, a remote attacker can use DNS rebinding to bypass the browser's Same-Origin Policy (SOP). This allows the attacker to send arbitrary requests to the local MCP server, potentially invoking tools or accessing resources on behalf of the user. The vulnerability is addressed in version 1.23.0, which enables DNS rebinding protection by default for localhost/127.0.0.1 addresses.
Affected products
- Model Context Protocol (MCP) mcp < 1.23.0
Identifiers
- CVE-2025-66416
- GHSA-9h52-p55h-vw2f
- PYSEC-2026-1617
Timeline
- 2025-12-02: disclosed
- 2025-12-02: patched: Fixed in version 1.23.0
- 2025-12-02: advisory