PT-2026-135831
CVE-2026-115563
·
Published
2026-11-02
·
Updated
2026-11-16
Description by
CVSS 3.1
7.5
HighMetricsAV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Name of the Vulnerable Software and Affected Versions
Model Context Protocol Python SDK versions 1.9.1 through 1.29.9
Model Context Protocol Python SDK versions 2.0.0 through 2.1.9
Description
OAuth client support in
mcp.client.auth allows credentials to be sent to an authorization server selected by an untrusted MCP server. Specifically, ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider cannot identify the authorization server that owns their credentials. Affected HTTP clients using these providers, OAuthClientProvider, or the deprecated RFC7523OAuthClientProvider may disclose a client secret, authorization code, PKCE code verifier, or signed client assertion. This issue does not affect MCP servers, stdio clients, or clients that attach their own tokens or headers.Recommendations
Update to version 1.30.0 or 2.2.0.
For
ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider, configure the issuer= parameter after updating.
Replace the deprecated RFC7523OAuthClientProvider as it lacks an issuer option.
Clear stored OAuth client information to register again or manually update pre-registered records with the correct issuer.Exploitability
Exploit
Fix
Impacts
Vendors
Affected products
Found an issue in the description? Have something to add? Feel free to write us 👾