Read the docs

Model Context Protocol Python SDK OAuth client leaks credentials

Priority LOW 36CWE-345Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass, Information disclosure
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-345 and CWE-522.

Summary

The Model Context Protocol Python SDK, from 1.9.1 before 1.30.0 and from 2.0.0a1 before 2.2.0, has OAuth client code in mcp.client.auth that can send credentials to an authorization server chosen by an untrusted MCP server. A malicious MCP server can cause HTTP clients using these providers to disclose a client secret, authorization code, PKCE code verifier, or signed client assertion (CWE-522). The affected providers are ClientCredentialsOAuthProvider, PrivateKeyJWTOAuthProvider, OAuthClientProvider, and the deprecated RFC7523OAuthClientProvider.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
Fix Fixed python-sdk (modelcontextprotocol): 1.30.0, 2.2.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
MLflowpython-sdk1.9.1 to before 1.30.0; 2.0.0a1 to before 2.2.01.30.0, 2.2.0Patch availableCNA
  • python-sdk VendorMLflow Affected 1.9.1 to before 1.30.0; 2.0.0a1 to before 2.2.0 Fixed in 1.30.0, 2.2.0 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:lfprojects:mcp_python_sdk:*:*:*:*:*:*:*:*——MLflow
  • cpe:2.3:a:lfprojects:mcp_python_sdk:*:*:*:*:*:*:*:* Versions — — ·MLflow

Remediation

Upgrade to version 1.30.0 or 2.2.0. After upgrading, callers of ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider must set issuer=, and the deprecated RFC7523OAuthClientProvider must be replaced because it has no issuer option. Stored OAuth client information without an issuer must be cleared once to register again, or a manually pre-registered record must be updated with its issuer.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA python-sdk (modelcontextprotocol) Fixed in 1.30.0, 2.2.0

Timeline

  1. 2026-11-16 Threatist record created from CVE-2026-115563
  2. 2026-11-16 CISA SSVC decision points changed

References

  • TI-2026-46366 Server-side request forgery in MLflow webhook delivery KEVCVSS 3.1CRITICAL 9.3
  • TI-2023-03518 Absolute Path Traversal in mlflow/mlflow CVSS 3.1CRITICAL 10.0
  • TI-2023-01113 Path Traversal: '\..\filename' in mlflow/mlflow CVSS 3.1CRITICAL 9.8
  • TI-2025-31759 Redis Lua Use-After-Free may lead to remote code execution CVSS 3.1CRITICAL 10.0
  • TI-2026-81527 Code execution via scorer deserialization in MLflow servers CVSS 3.1CRITICAL 9.8
  • TI-2025-14028 Command Injection in mlflow/mlflow CVSS 3.1CRITICAL 10.0
See all 177 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences