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
·
Updated

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 clientsecret, authorization code, PKCE codeverifier, 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.

Affected Software

1 affected component
pypi/mcp>=1.9.1<1.30.0, >=2.0.0<2.2.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.30.0
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.2.0
  3. Configuration

    Configure issuer= to identify the authorization server that owns the credentials.

    ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider issuer
  4. Operational

    After upgrading, clear stored OAuth client information once to register again, or update a manually pre-registered record with its issuer.

Event History

Nov 16, 2026
CVE Published
via MITRE·08:24 PM
Data Sourced
via MITRE·08:24 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which client deployments are exposed?

Affected deployments are HTTP clients using ClientCredentialsOAuthProvider, PrivateKeyJWTOAuthProvider, OAuthClientProvider, or the deprecated 1.x RFC7523OAuthClientProvider. MCP servers, stdio clients, and clients that attach their own tokens or headers are not affected.

2

What could an untrusted server obtain?

The affected OAuth flows can disclose a client_secret, authorization code, PKCE code_verifier, or signed client assertion to an authorization server selected by the untrusted MCP server. ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider cannot independently identify the authorization server that owns their credentials.

3

Does exploitation require a person to sign in?

Interactive use of OAuthClientProvider requires a person to start sign-in. The unattended ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider do not require that interaction.

4

What configuration changes are required after upgrading?

Callers using ClientCredentialsOAuthProvider or PrivateKeyJWTOAuthProvider must configure issuer=; omitting it still follows the authorization server advertised by the MCP server. Replace the deprecated RFC7523OAuthClientProvider because it has no issuer option, and update any stored client registration that lacks an issuer because it remains unbound after upgrading.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203