UTC
High

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
What it is

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

What to do

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.

Affected
PackageRegistryAffectedFixed in
@modelcontextprotocol/clientnpm>= 2.0.0, < 2.2.02.2.0
@modelcontextprotocol/sdknpm>= 1.12.0, < 1.31.01.31.0
Downstream in the Official MCP Registry

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