Model Context Protocol Python SDK: HTTP client transports followed cross-origin redirects carrying custom headers and bodies

Summary In affected versions, the SDK's Streamable HTTP and SSE client transports followed HTTP redirects to any host. If the configured MCP endpoint answered with a redirect to a different origin: custom headers set on the client (for example an X-API-Key credential) were sent to that origin, and on a 307 or 308 redirect the request body was re-sent there too. The SDK's OAuth client providers followed redirects on their own discovery, registration and token requests in the same way. A lone Authorization bearer header was not exposed; the HTTP library already drops it on cross-origin redirects. Anyone able to make an endpoint you trust redirect elsewhere (a stale redirect to a lapsed domain, a misrouted proxy rule, redirect logic an attacker can influence) could capture that material. A server that is itself malicious gains nothing this way; it already receives your requests directly. Am I affected? Yes, if your code uses the SDK as an MCP client over HTTP through any of: streamablehttpclient (on 2.x also Client given an http:// or https:// URL) streamablehttpclient or sseclient ClientSessionGroup with HTTP server parameters the internal createmcphttpclient helper This includes an…

curl https://cve.zerocrew.in/api/cve/CVE-2026-116685