Medium

Model Context Protocol Python SDK: Client fetched server-chosen $ref URLs while validating tool results against output schemas

  • Disclosed: 27.10.2026
  • Updated: 27.10.2026 23:17

Summary

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 the process for as long as it held the connection.

Am I affected?

Yes, if your application uses the SDK as an MCP client (ClientSession over any transport, ClientSessionGroup, or the 2.x Client) and calls tools on servers you do not fully control. There was no setting that turned the validation off.

Affected versions: 1.10.0 through 1.29.1, and 2.0.0 through 2.1.1.

Not affected: applications that only build servers. If nothing in your code uses ClientSession, ClientSessionGroup or the 2.x Client class, you are not affected.

Fix

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 #.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) mcp >= 2.0.0, < 2.2.0, >= 1.10.0, < 1.30.0 2.2.0, 1.30.0

References

CVSS score 6.5/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Weakness (CWE)
CWE-918
Platform
Python (PyPI)
Package
mcp
Disclosed
27.10.2026
Updated
27.10.2026 23:17

Sources and licenses

OSV / GitHub Advisory Database - GHSA-rwrf-2pqf-9j8j - CC BY 4.0

Vulnerability history: mcp

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (11) in the archive
Total entries
11
First → latest
07.2025 11.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • High 7
  • Medium 4

Disclosures per year

  1. 2025: 3
  2. 2026: 8
Severity:
  1. High · 7.5 CVE-2026-115563 >= 2.0.0a1, < 2.2.0, >= 1.9.1, < 1.30.0 2.2.0, 1.30.0
  2. Model Context Protocol Python SDK: Client fetched server-chosen $ref URLs while validating tool results against output schemas this entry
    Medium · 6.5 CVE-2026-116686 >= 2.0.0, < 2.2.0, >= 1.10.0, < 1.30.0 2.2.0, 1.30.0

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.