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
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.
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 .
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @modelcontextprotocol/client | npm | >= 2.0.0, < 2.3.0 | 2.3.0 |
| @modelcontextprotocol/sdk | npm | < 1.32.0 | 1.32.0 |
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
- CriticalPhoenix: Format String Injection in applyChatTemplatearize-phoenix
- CriticalFlowise: Unauthenticated OAuth2 token refresh endpoint returns access tokens — enables token theft for any connected serviceflowise
- CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
- CriticalvLLM has RCE In Video Processingvllm
- HighConfig revision hashes could expose password verifiersopenclaw
- Highn8n: Shared Credential Header Leak via HTTP Request Pagination Expressionn8n, n8n, n8n
- 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
- HighMCP TypeScript SDK: Experimental tasks were not tied to the session that created them@modelcontextprotocol/sdk
- HighMCP TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation@modelcontextprotocol/sdk, @modelcontextprotocol/server
- HighMCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server@modelcontextprotocol/client, @modelcontextprotocol/sdk
- High@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse@modelcontextprotocol/sdk
- 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.