CVE-2026-115563
MCP Python OAuth clients could disclose credentials to an untrusted authorization server
modelcontextprotocol · Model Context Protocol Python SDK
First documented disclosure · Review checkpoint
Summary
An untrusted MCP server could direct OAuth credentials to an authorization server it selected.
Severity and exploitation evidence
High · 7.5/10 · CVSS 3.1. Severity source.
Exploitation not established: Malicious exploitation status remains unverified in the reviewed sources.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
Credential ownership was insufficiently bound to an expected OAuth issuer.
Conditions required
Affected HTTP OAuth providers are used. Interactive sign-in requires user initiation, while unattended providers can proceed automatically.
Potential impact
Client secrets, authorization codes, PKCE verifiers or signed assertions can reach another authorization server.
Affected versions and configurations
1.9.1 through versions before 1.30.0, and 2.0.0a1 through versions before 2.2.0.
Fix and mitigation status
1.30.0 and 2.2.0, with issuer configuration and registration repair.
Practical next steps
Upgrade. Configure the expected issuer on client-credentials and private-key providers, replace deprecated RFC7523OAuthClientProvider, and clear stored client registration once or bind manually registered records to their issuer.
Operating lesson
Bind reusable OAuth credentials to the authorization server that owns them.
Evidence and limits
Original disclosure 2026-09-28. The CVE Program published this record 2026-11-16. The advisory limits scope to HTTP OAuth client support. Correct issuer configuration and existing-registration repair are part of remediation.
Sources
- GitHub_M CVE authority record
Primary source ·
- Model Context Protocol Python SDK original advisory
Primary source ·
- ENISA EUVD-2026-126629
Primary source ·