MCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server
CVE-2026-104850 · GHSA-6qxp-vccf-f47h · published 2026-10-06
- Severity
- High
- CVSS score
- 7.5
- Chance of exploitation (EPSS)
- 0.28%
- Fixed in
- 2.2.0
- Exploitation No known exploitation
- Automatable Yes
- Technical impact Partial
- CISA SSVC
In affected versions, the SDK's OAuth client let the MCP server decide which authorization server received the client's OAuth credentials. Credentials were not tied to the authorization server they belong to. A malicious or compromised MCP server could name its own authorization server. With no user interaction, the client would send it: the refreshtoken and clientsecret stored from an earlier sign-in the client_secret or signed assertion configured on a bundled provider
Upgrade @modelcontextprotocol/client to 2.2.0 or later, and @modelcontextprotocol/sdk to 1.31.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.31.0 or later 2.x: @modelcontextprotocol/client 2.2.0 or later, and @modelcontextprotocol/core 2.2.0 or later if you import it directly The client now records the authorization server as issuer on saved credentials and does not send them to a different one. The user signs in again, or the call throws. In the following cases, upgrading to the patched version is not enough. You also need to make a change: Bundled providers (ClientCredentialsProvider, PrivateKeyJwtProvider, StaticPrivateKeyJwtProvider, CrossAppAccessProvider): pass expectedIssuer, for example . Without it they still use whichever authorization server the MCP server names.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @modelcontextprotocol/client | npm | >= 2.0.0, < 2.2.0 | 2.2.0 |
| @modelcontextprotocol/sdk | npm | >= 1.12.0, < 1.31.0 | 1.31.0 |
353 registered MCP servers install an affected version today, by the dependency versions a fresh install resolves.
- ai.makerportal/compute@modelcontextprotocol/sdk@1.30.0
- ai.mentu/navigator@modelcontextprotocol/sdk@1.29.0
- ai.myspaice/spaces@modelcontextprotocol/sdk@1.29.0
- ai.sanctuaryprotocol/sanctuary@modelcontextprotocol/sdk@1.30.0
- ai.satohub/kit@modelcontextprotocol/sdk@1.30.1
- ai.sendshort/sendshort@modelcontextprotocol/sdk@1.30.0
- app.somiya/mcp@modelcontextprotocol/sdk@1.30.0
- cn.housingsentinel/housing-sentinel@modelcontextprotocol/sdk@1.29.0
- com.apideck/mcp@modelcontextprotocol/sdk@1.25.2
- com.binaryandthread/store@modelcontextprotocol/sdk@1.29.0
- com.blackduck/mcp-server@modelcontextprotocol/sdk@1.29.0
- com.brainfeather/mcp@modelcontextprotocol/sdk@1.30.0
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- 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
- 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
- HighModel Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default@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.