Technical impact
The Model Context Protocol Python SDK performs JSON schema validation of output schemas using jsonschema’s default resolver. When a server supplies a malicious outputSchema that contains a $ref pointing to any HTTP, HTTPS, or file URL, the client will fetch that URL during validation. This can trigger blind network requests, unauthorized local file reads, and can stall every session in the process because the resolution runs synchronously on the event loop without a timeout.
Affected Systems
The vulnerable range includes all deployments of the Model Context Protocol Python SDK from version 1.10.0 up to but not including 1.30.0, and from 2.0.0 up to but not including 2.2.0. The issue was resolved in releases 1.30.0 and 2.2.0.
Risk and Exploitability
The vulnerability has a CVSS score of 6.5, indicating a moderate risk level. The EPSS score is < 1%, suggesting a very low exploitation probability, and it is not listed in the CISA KEV catalog. A malicious server that can instruct the SDK to validate a schema with a remote or local $ref can trigger blind network requests or local file reads, or consume all of the client’s event-loop resources by blocking the resolution step without a timeout. Therefore, while not enabling remote code execution, the flaw poses a significant threat to confidentiality and availability for any systems that rely on this SDK to validate server-supplied schemas.
Github GHSA