Model Context Protocol Python SDK: OAuth client could send credentials to an authorization server chosen by the MCP server
Summary
| CVE | CVE-2026-115563 |
|---|---|
| State | PUBLISHED |
| Assigner | GitHub_M |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-16 21:17:20 UTC |
| Updated | 2026-11-16 22:18:13 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 7.5 HIGH from [email protected]
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Problem Types: CWE-345 | CWE-522 | CWE-345 CWE-345: Insufficient Verification of Data Authenticity | CWE-522 CWE-522: Insufficiently Protected Credentials
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 7.5 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| 3.1 | CNA | DECLARED | 7.5 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
NoneAvailability
NoneCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Modelcontextprotocol | Python-sdk | affected >= 1.9.1, < 1.30.0 | Not specified |
| CNA | Modelcontextprotocol | Python-sdk | affected >= 2.0.0a1, < 2.2.0 | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/modelcontextprotocol/python-sdk/commit/d060b36e1d095ef6e93e07... | [email protected] | github.com | |
| github.com/modelcontextprotocol/python-sdk/pull/3398 | [email protected] | github.com | |
| github.com/modelcontextprotocol/python-sdk/pull/3435 | [email protected] | github.com | |
| github.com/modelcontextprotocol/python-sdk/commit/979208c1157661eac0151f... | [email protected] | github.com | |
| github.com/modelcontextprotocol/python-sdk/releases/tag/v1.30.0 | [email protected] | github.com | |
| github.com/modelcontextprotocol/python-sdk/security/advisories/GHSA-qx49... | [email protected] | github.com | |
| github.com/modelcontextprotocol/python-sdk/pull/3431 | [email protected] | github.com | |
| github.com/modelcontextprotocol/python-sdk/commit/3eed7ce0a6aba76e8d94c4... | [email protected] | github.com | |
| github.com/modelcontextprotocol/python-sdk/releases/tag/v2.2.0 | [email protected] | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.