UTC
High

Model Context Protocol Python SDK: OAuth client could send credentials to an authorization server chosen by the MCP server

CVE-2026-115563 · GHSA-qx49-fqc8-xw99 · published 2026-11-19

Severity
High
CVSS score
7.5
Chance of exploitation (EPSS)
0.32%
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 support (mcp.client.auth) let the MCP server a client connected to decide where the client's OAuth credentials were sent: the authorization server metadata issuer was not validated on every discovery path, and stored or pre-provisioned client credentials were not bound to the authorization server they belong to. A malicious or compromised MCP server could therefore direct them to a token endpoint of its choosing: by naming its own authorization server in its protected resource metadata, or by publishing none and serving metadata that presents the user's real authorization server as the issuer. …

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 2.2.0 (2.x) or 1.30.0 (1.x) or later. If you use ClientCredentialsOAuthProvider or PrivateKeyJWTOAuthProvider, upgrading changes nothing until you also pass issuer= (for example issuer="https://auth.example.com"): Without it they still follow whichever authorization server the MCP server advertises. Omitting it now emits a deprecation warning, and it becomes required in 3.0. On 1.30.0 it is a DeprecationWarning, which Python hides by default. The deprecated 1.x RFC7523OAuthClientProvider has no issuer option. Move to one of these two providers. …

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

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