In affected versions, the SDK's OAuth client support (mcp.client.auth) let the MCP server a client connected to decide where the client's OAuth credentials were sent:
issuer was not validated on every discovery path, andA malicious or compromised MCP server could therefore direct them to a token endpoint of its choosing:
issuer.It would then receive the client_secret, authorization code and PKCE code_verifier meant for that real server (or, with PrivateKeyJWTOAuthProvider, a signed client assertion).
Yes, if both of these hold:
OAuthClientProvider, ClientCredentialsOAuthProvider, PrivateKeyJWTOAuthProvider or the deprecated 1.x RFC7523OAuthClientProvider as the transport's auth handler;Affected versions:
issuer check and no credential binding on any path.403 insufficient_scope.ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider had no way to name the authorization server their credentials belong to.Not affected:
The rating is scored for the unattended providers. With the interactive OAuthClientProvider a person has to start the sign-in; scored that way it is 6.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N).
Upgrade to mcp 2.2.0 (2.x) or 1.30.0 (1.x) or later.
If you use ClientCredentialsOAuthProvider or PrivateKeyJWTOAuthProvider, upgrading changes nothing until you also pass issuer= (for example issuer="https://auth.example.com"):
DeprecationWarning, which Python hides by default.RFC7523OAuthClientProvider has no issuer option. Move to one of these two providers.In the fixed versions the client also:
issuer differs, with OAuthFlowError;After upgrading:
issuer on that record instead.On earlier versions there is no workaround other than connecting OAuth-enabled clients only to MCP servers you trust.
{
"cwe_ids": [
"CWE-345",
"CWE-522"
],
"github_reviewed": true,
"github_reviewed_at": "2026-11-19T22:45:40Z",
"nvd_published_at": "2026-11-16T21:17:20Z",
"severity": "HIGH"
}