CVE-2026-115563

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

Published Nov 16, 2026 CVSS 3.1 · 7.5 High EPSS n/a KEV · Not listed
Description
The Model Context Protocol Python SDK is the official Python SDK for Model Context Protocol servers and clients. From 1.9.1 until 1.30.0 and 2.2.0, OAuth client support in mcp.client.auth can send credentials to an authorization server chosen by an untrusted MCP server. ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider cannot identify the authorization server that owns their credentials. Affected HTTP clients using those providers, OAuthClientProvider, or the deprecated 1.x RFC7523OAuthClientProvider can disclose a client_secret, authorization code, PKCE code_verifier, or signed client assertion. MCP servers, stdio clients, and clients that attach their own tokens or headers are not affected. Interactive OAuthClientProvider use requires a person to start sign-in, while the unattended providers do not. For ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider, callers must configure issuer= after upgrading because omission still follows the MCP server's advertised authorization server, and the deprecated RFC7523OAuthClientProvider must be replaced because it has no issuer option. A stored client registration without an issuer remains unbound after upgrading, so stored OAuth client information must be cleared once to register again or a manually pre-registered record must be updated with its issuer. This issue is fixed in versions 1.30.0 and 2.2.0.

Analysis

AI-generated

Technical impact

The vulnerability in the Model Context Protocol Python SDK allows an OAuth client during authentication to send its credentials to an authorization server chosen by the MCP server. As the client credentials, authorization code, PKCE code verifier, or signed client assertion can be transmitted to an arbitrary server, the attacker gains sensitive authentication material. This leads to a confidentiality breach that could subsequently permit unauthorized access to protected resources. The weakness aligns with CWE-345 (Authority Control) and CWE-522 (Data at Rest).

Affected Systems

Affected installations are those of the Model Context Protocol Python SDK from version 1.9.1 up through 1.30.0, as well as version 2.2.0. Those using the client providers ClientCredentialsOAuthProvider, PrivateKeyJWTOAuthProvider, OAuthClientProvider, or the deprecated RFC7523OAuthClientProvider are vulnerable. Servers that specify issuer information after upgrade are not impacted, while the rest remain at risk until updated.

Risk and Exploitability

The CVSS score of 7.5 indicates a high severity. EPSS is not available, so the exploitation probability cannot be quantified, but because the flaw depends on a trusting relationship with an MCP server, the issue is unlikely to see widespread exploitation unless the server is malicious or misconfigured. The vulnerability is not listed in CISA KEV. A trusted MCP server can select a rogue authorization endpoint, thereby exposing credentials. Mitigation requires moving to the latest patched releases and ensuring correct issuer configuration to bind credentials to the intended server.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Model Context Protocol Python SDK to v1.30.0 or v2.2.0, whichever matches your environment, to obtain the fixed authorization server handling logic.
  • After upgrading, set the 'issuer' attribute for ClientCredentialsOAuthProvider, PrivateKeyJWTOAuthProvider, and any other OAuth client provider to match the desired authorization server, preventing the SDK from following the MCP server’s advertised endpoint.
  • Clear any stored OAuth client registrations that lack an issuer or replace them with records that explicitly include the issuer, as these unbound registrations remain vulnerable even after the upgrade.
  • Replace any use of the deprecated RFC7523OAuthClientProvider, which lacks an issuer option, with a supported provider that honors the issuer setting.

Generated by OpenCVE AI on November 16, 2026 at 21:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Modelcontextprotocol
Modelcontextprotocol python-sdk
Vendors & Products Modelcontextprotocol
Modelcontextprotocol python-sdk
Type Values Removed Values Added
Description The Model Context Protocol Python SDK is the official Python SDK for Model Context Protocol servers and clients. From 1.9.1 until 1.30.0 and 2.2.0, OAuth client support in mcp.client.auth can send credentials to an authorization server chosen by an untrusted MCP server. ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider cannot identify the authorization server that owns their credentials. Affected HTTP clients using those providers, OAuthClientProvider, or the deprecated 1.x RFC7523OAuthClientProvider can disclose a client_secret, authorization code, PKCE code_verifier, or signed client assertion. MCP servers, stdio clients, and clients that attach their own tokens or headers are not affected. Interactive OAuthClientProvider use requires a person to start sign-in, while the unattended providers do not. For ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider, callers must configure issuer= after upgrading because omission still follows the MCP server's advertised authorization server, and the deprecated RFC7523OAuthClientProvider must be replaced because it has no issuer option. A stored client registration without an issuer remains unbound after upgrading, so stored OAuth client information must be cleared once to register again or a manually pre-registered record must be updated with its issuer. This issue is fixed in versions 1.30.0 and 2.2.0.
Title Model Context Protocol Python SDK: OAuth client could send credentials to an authorization server chosen by the MCP server
Weaknesses CWE-345
CWE-522
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

  • CWE-522

    Insufficiently Protected Credentials

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 16, 2026, 9:27 PM
Reserved
Oct 22, 2026, 10:53 PM
Status
Received
Published
Nov 16, 2026, 9:17 PM
Modified
Nov 16, 2026, 10:18 PM