CVE-2026-115563
Last modified
CVE-2026-115563 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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.
Description
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| modelcontextprotocol | python-sdk | >= 1.9.1, < 1.30.0; >= 2.0.0a1, < 2.2.0 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-115563?
How severe is CVE-2026-115563?
How do I fix CVE-2026-115563?
How Strix Helps
- Same Subject, Wrong User: A Cross-Issuer Account Takeover in n8nStrix found an identity-binding bug in n8n's token-exchange flow enabling account takeover.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-115548The Quttera ThreatSign – Web Malware Scanner for WordPress p…7.2
- CVE-2026-11555A vulnerability was identified in D-Link DGS-1100-08PD 1.00.…7.5
- CVE-2026-115554IBM Tivoli Netcool/OMNIbus 8.1.0 through 8.1.0.41 is vulnera…6.4
- CVE-2026-115557Python has added a denylist for known compromised certificat…9.4
- CVE-2026-115559IMAP4.starttls() wraps the socket in TLS but leaves self._re…6.3
- CVE-2026-11556A security flaw has been discovered in Tenda F451 1.0.0.7/1.…8.8
- CVE-2026-115567Tokio is a runtime for writing applications with Rust. In 1.…5.8
- CVE-2026-115569Fallow is a codebase intelligence tool for TypeScript and Ja…3.3
- CVE-2026-11557A weakness has been identified in Tenda F451 1.0.0.7/1.0.0.9…8.8
- CVE-2026-115570Electron is a framework for writing cross-platform desktop a…7.4
- CVE-2026-115572pypdf is a free and open-source pure-python PDF library. Pri…7.1
- CVE-2026-115573OpenEMR is a free and open source electronic health records …8.1
Are you affected by CVE-2026-115563?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
