AI Stack Alert Medium CVE-2026-116686 For AppSec, AI Eng, SOC / IR AI-assisted
CVE-2026-116686: MCP Python SDK client fetched server-chosen $ref URLs during output validation
The MCP Python SDK client validated tool results against outputSchema using jsonschema's default resolver, which fetched unresolved $ref URLs (http, https, file). A connected server could make the client request URLs or read local files on each tool call, and the synchronous fetch had no timeout. Fixed in mcp 1.30.0 and 2.2.0.
Why it matters
Applications using the MCP Python SDK as a client against servers they do not fully control can be used for server-side request and local file access from the client's network position, and a stalled target can freeze all sessions in the process.
Do this
- Upgrade mcp to 1.30.0 or later (1.x line) or 2.2.0 or later (2.x line).
- Until upgraded, call tools only on servers you fully trust.
- As a partial stopgap, skip tools whose outputSchema contains an $id, or a $ref/$dynamicRef that does not start with '#'.
- Inventory services that use ClientSession, ClientSessionGroup, or the 2.x Client class to identify exposed deployments.
Exploit Clock
Exploitation unlikely (for now)
- EPSS 0.34%
Signals
- NoCISA KEV
- 6.5CVSS
- 0.34%EPSS
- 28/100Priority
- 90%Confidence
Evidence
“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”
“Upgrade to `mcp` 1.30.0 (1.x) or 2.2.0 (2.x) or later.”
Sources
Affected / related
mcp, Server-chosen $ref URL fetching during JSON Schema validation
Published 2026-10-27 21:05 UTC · updated 2026-11-08 02:39 UTC · AI-assisted summary, checked against quoted sources · How we score