UTC
Medium

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

CVE-2026-116685 · GHSA-5h93-6whr-6q8j · published 2026-10-27

Severity
Medium
CVSS score
5.9
Chance of exploitation (EPSS)
0.40%
Fixed in
2.2.0
  • Exploitation No known exploitation
  • Automatable No
  • Technical impact Partial
  • CISA SSVC
What it is

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.

What to do

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; no code changes are needed. The transports, and the OAuth providers' own requests, now follow a redirect only when it stays on the endpoint's origin (same scheme, host and port, or an http to https upgrade on the same host) and keeps the request method. Any other redirect is not followed and the request fails with an error naming the target (MCPError on 2.x, httpx.HTTPStatusError on 1.x), whichever HTTP client the transport uses. The internal createmcphttpclient helper no longer turns redirect following on, so code calling it directly now receives the redirect response instead.

Affected
PackageRegistryAffectedFixed in
mcpPyPI>= 1.8.0, < 1.30.01.30.0
mcpPyPI>= 2.0.0, < 2.2.02.2.0
Downstream in the Official MCP Registry

46 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.cyberspf/mcpmcp@1.9.4
  • 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
All 46 servers on the trace →

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].