UTC
Medium

MCP TypeScript client SDK: HTTP client transports and OAuth requests followed cross-origin redirects and re-sent custom headers and request

CVE-2026-111769 · GHSA-6prh-2h8m-c8cw · published 2026-10-20 · updated 2026-11-03

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

In affected versions, the SDK's HTTP client transports and OAuth requests followed redirects to any origin. If an MCP server or authorization server redirected a request to another origin, that origin received custom request headers (such as an X-API-Key set in requestInit.headers) and the mcp-session-id header. On a 307 or 308 it also received the request body, including OAuth token requests with their refreshtoken and clientsecret. On current runtimes fetch already drops the Authorization header across origins.

What to do

Upgrade @modelcontextprotocol/client to 2.3.0 or later, and @modelcontextprotocol/sdk to 1.32.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: 1.x: @modelcontextprotocol/sdk 1.32.0 or later 2.x: @modelcontextprotocol/client 2.3.0 or later Redirects are now followed only within the same origin, and not at all in browsers. If your MCP server or authorization server redirects to another origin on purpose, configure the final URL instead. Setting redirectPolicy: 'follow' on a transport restores the old behaviour and the exposure. If a redirect may have reached a host you do not control, rotate the API keys and client_secret your application held and revoke its tokens. If you cannot upgrade yet, pass a fetch that refuses redirects, for example .

Affected
PackageRegistryAffectedFixed in
@modelcontextprotocol/clientnpm>= 2.0.0, < 2.3.02.3.0
@modelcontextprotocol/sdknpm< 1.32.01.32.0
Downstream in the Official MCP Registry

448 registered MCP servers install an affected version today, by the dependency versions a fresh install resolves.

  • ai.kloudy/kloudy@modelcontextprotocol/sdk@1.31.0
  • ai.makerportal/compute@modelcontextprotocol/sdk@1.30.0
  • ai.maxwellinternational/data@modelcontextprotocol/sdk@1.31.0
  • ai.mentu/navigator@modelcontextprotocol/sdk@1.29.0
  • ai.myspaice/spaces@modelcontextprotocol/sdk@1.29.0
  • ai.pixeldojo/mcp@modelcontextprotocol/sdk@1.4.1
  • ai.sanctuaryprotocol/sanctuary@modelcontextprotocol/sdk@1.30.0
  • ai.satohub/kit@modelcontextprotocol/sdk@1.30.1
  • ai.sendshort/sendshort@modelcontextprotocol/sdk@1.30.0
  • ai.wild-card/deepcontext@modelcontextprotocol/sdk@0.6.1
  • app.somiya/mcp@modelcontextprotocol/sdk@1.30.0
  • cheap.doc/mcp@modelcontextprotocol/sdk@1.31.0
All 448 servers on the trace →
Also in @modelcontextprotocol/client, @modelcontextprotocol/sdk
  1. HighMCP TypeScript SDK: HTTP server transports and handlers did not limit request body size or JSON-RPC batch length@modelcontextprotocol/hono, @modelcontextprotocol/node, @modelcontextprotocol/sdk, @modelcontextprotocol/server
  2. HighMCP TypeScript SDK: Experimental tasks were not tied to the session that created them@modelcontextprotocol/sdk
  3. HighMCP TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation@modelcontextprotocol/sdk, @modelcontextprotocol/server
  4. HighMCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server@modelcontextprotocol/client, @modelcontextprotocol/sdk
  5. High@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse@modelcontextprotocol/sdk
  6. HighAnthropic's MCP TypeScript SDK has a ReDoS vulnerability@modelcontextprotocol/sdk

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