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.