Model Context Protocol Python SDK: Client fetched server-chosen $ref URLs while validating tool results against output schemas
CVE-2026-116686 · GHSA-rwrf-2pqf-9j8j · published 2026-10-27
- Severity
- Medium
- CVSS score
- 6.5
- Chance of exploitation (EPSS)
- 0.34%
- Fixed in
- 2.2.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
In affected versions, when a connected MCP server declared an outputSchema for a tool, the SDK's client validated each call_tool result with jsonschema's default resolver, which fetches any $ref it cannot resolve locally by opening the URL. A server could therefore put an http://, https:// or file:// reference in a tool's output schema and make the client: request that URL, or read that local file, from the client's own network position on every call of the tool (the content was used only as a schema and never sent back to the server), and stall: the fetch ran synchronously on the event loop with no timeout, so a target that accepted the connection and then went quiet froze every session in…
Upgrade mcp to 2.2.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.
Upgrade to mcp 1.30.0 (1.x) or 2.2.0 (2.x) or later. The client now resolves references only within the schema document the server sent (plus the standard JSON Schema metaschemas), so result validation performs no network or file access. A tool whose output schema points outside its own document fails at call time with RuntimeError (Invalid schema for tool ...); in-document references such as #/$defs/... work as before. Until you can upgrade, call tools only on servers you trust. As a partial stopgap, skip tools whose outputSchema contains an $id, or a $ref / $dynamicRef that does not start with #.
43 registered MCP servers install an affected version today, by the dependency versions a fresh install resolves.
- ai.datavidence/datavidence-financialsmcp@2.1.1
- ai.solwyn/solwynmcp@2.1.1
- com.browser-use/browser-usemcp@2.1.1
- com.lucidlink/mcpmcp@2.0.0
- com.nautaai/holster-mcpmcp@1.27.2
- io.github.abhichandra21/promptheusmcp@1.12.4
- io.github.Alejandrehl/kainext-binance-mcpmcp@1.29.0
- io.github.amin-ale/mcp-quickbooksmcp@1.28.1
- io.github.AndreySukhanov/summarix-telegrammcp@1.12.4
- io.github.AS-XS/ai-pensieve-mcpmcp@2.1.1
- io.github.ashlesh-t/cognirepomcp@1.27.0
- io.github.astrogilda/waitbusmcp@1.28.1
- CriticalMLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebindingmlflowExploited
- Critical@zereight/mcp-gitlab Vulnerable to Server-Side Request Forgery@zereight/mcp-gitlab
- CriticalSSRF + LLM API key exfiltration via user-controlled basepath / baseUrl in 8 chat-model nodesflowise, flowise-components
- CriticalLocalAI POST /models/apply permits unauthenticated server-side request forgery through gallery URLsgithub.com/mudler/LocalAI
- CriticalFastMCP OpenAPI Provider has an SSRF & Path Traversal Vulnerabilityfastmcp
- CriticalBentoML SSRF Vulnerability in File Upload Processingbentoml
- HighModel Context Protocol Python SDK: OAuth client could send credentials to an authorization server chosen by the MCP servermcp, mcp
- HighHTTP server transports and OAuth endpoints read request bodies with no size limitmcp, mcp
- HighMCP Python SDK: Experimental task handlers allow any client to access and cancel other clients' tasksmcp
- HighMCP Python SDK: HTTP transports serve session requests without verifying the authenticated principalmcp
- HighMCP Python SDK: WebSocket server transport does not support Host/Origin validationmcp
- HighModel Context Protocol (MCP) Python SDK does not enable DNS rebinding protection by defaultmcp
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.