CVE-2026-115563 json
Model Context Protocol Python SDK: OAuth client could send credentials to an authorization server chosen by the MCP server
published last mo. modified yesterday also EUVD-2026-126629 , GHSA-qx49-fqc8-xw99
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository modelcontextprotocol/python-sdk. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi mcp 1.30.0, 2.2.0
- github.com/modelcontextprotocol/python-sdk@3eed7ce commit
- github.com/modelcontextprotocol/python-sdk@979208c commit
- github.com/modelcontextprotocol/python-sdk@d060b36 commit
- github.com/modelcontextprotocol/python-sdk#3398 pull request
- github.com/modelcontextprotocol/python-sdk#3431 pull request
- github.com/modelcontextprotocol/python-sdk#3435 pull request
- github.com/modelcontextprotocol/python-sdk/releases/tag/v1.30.0 release
- github.com/modelcontextprotocol/python-sdk/releases/tag/v2.2.0 release
Is CVE-2026-115563 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-17).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | mcp | >=2.0.0a1, <2.2.0 >=1.9.1, <1.30.0 |
2.2.0 1.30.0 |
Affected products
- modelcontextprotocol python-sdk
Classification
References
- github.com /modelcontextprotocol/python-sdk/pull/3398
- github.com /modelcontextprotocol/python-sdk/pull/3431
- github.com /modelcontextprotocol/python-sdk/pull/3435
- github.com /modelcontextprotocol/python-sdk/commit/3eed7ce0a6aba76e8d94c4cfb9b266f41935392c
- github.com /modelcontextprotocol/python-sdk/commit/979208c1157661eac0151f90974a1f96528003fa
- github.com /modelcontextprotocol/python-sdk/commit/d060b36e1d095ef6e93e07ba5d59bb69b2ad449a
-
github.com
/modelcontextprotocol/python-sdk/security/advisories/GHSA-qx49-fqc8-xw99
advisory
- github.com /modelcontextprotocol/python-sdk/releases/tag/v1.30.0
- github.com /modelcontextprotocol/python-sdk/releases/tag/v2.2.0
Sources
- CVE List CVE-2026-115563
- NVD CVE-2026-115563
- Maintainer advisory GHSA-qx49-fqc8-xw99
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of modelcontextprotocol/python-sdk published their own advisory on GitHub. Reviewed sources take precedence over it.