MCP Server Security

MCP Python SDK client fetched URLs from server schemas

GitHub published advisory GHSA-rwrf-2pqf-9j8j (CVE-2026-116686, medium) on 27 Oct 2026: the MCP Python SDK client fetched server-chosen $ref URLs while checking tool results against output schemas. Affected versions are mcp 1.10.0 through 1.29.1 and 2.0.0 through 2.1.1. Fixes: 1.30.0 and 2.2.0.

Facts read on .

The advisory says that when a connected server declared an outputSchema for a tool, the SDK client validated each call_tool result with a default resolver that opens any reference it cannot resolve locally. A server could name an http, https or file reference in the schema, and the client would request that URL or read that local file from its own network position on every call of the tool. The advisory says the content was used only as a schema and never sent back to the server.

The advisory also describes a stall: the fetch ran synchronously with no timeout, so a target that accepted the connection and went quiet could freeze every session in the process. It rates the issue medium (CVSS 6.5) and says no setting turned the validation off.

Applications are affected if they use the SDK as a client (ClientSession, ClientSessionGroup or the 2.x Client) to call tools on servers they do not fully control. Server-only applications are not affected. The fix is mcp 1.30.0 or 2.2.0, which resolves references only inside the schema document the server sent. For an engineer who inventories MCP tooling, the check is which internal agents and scripts import the pip package mcp as a client and which version they pin.

Sources