CVE-2026-115563: modelcontextprotocol python-sdk · Insufficient Verification of Data Authenticity
Affects modelcontextprotocol python-sdkSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 2.2.0 or 1.30.0 soon.
Data as of 16 Nov 2026, 20:49 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 2.2.0, 1.30.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade python-sdk and modelcontextprotocol-python-sdk to 2.2.0 or 1.30.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| modelcontextprotocolpython-sdk | Affected
| Fixed in
|
| modelcontextprotocolpython-sdk | Affected
| Fixed in
|
PyPImodelcontextprotocol-python-sdkpkg:pypi/modelcontextprotocol-python-sdkOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Model Context Protocol Python SDK versions 1.30.0 or later, or 2.2.0 or later, where this issue is fixed. After upgrading, explicitly configure the issuer parameter for ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider to bind credentials to the correct authorization server. Replace the deprecated RFC7523OAuthClientProvider with supported providers that accept the issuer option. Clear stored OAuth client registrations without an issuer or update them with the correct issuer to prevent unbound credentials. No other actions are required.
Description
A vulnerability in the Model Context Protocol Python SDK versions from 1.9.1 up to but not including 1.30.0, and from 2.0.0a1 up to but not including 2.2.0, allows an untrusted MCP server to cause OAuth client providers to send sensitive credentials to an unauthorized authorization server. This affects ClientCredentialsOAuthProvider, PrivateKeyJWTOAuthProvider, OAuthClientProvider, and the deprecated RFC7523OAuthClientProvider. The issue is fixed in versions 1.30.0 and 2.2.0.
References
- github.com/modelcontextprotocol/python-sdk/security/advisories/GHSA-qx49-fqc8-xw99 (opens in a new tab)
- github.com/modelcontextprotocol/python-sdk/pull/3398 (opens in a new tab)
- github.com/modelcontextprotocol/python-sdk/pull/3431 (opens in a new tab)
- github.com/modelcontextprotocol/python-sdk/pull/3435 (opens in a new tab)
- github.com/modelcontextprotocol/python-sdk/commit/3eed7ce0a6aba76e8d94c4cfb9b266f41935392c (opens in a new tab)
- github.com/modelcontextprotocol/python-sdk/commit/979208c1157661eac0151f90974a1f96528003fa (opens in a new tab)
- github.com/modelcontextprotocol/python-sdk/commit/d060b36e1d095ef6e93e07ba5d59bb69b2ad449a (opens in a new tab)
- github.com/modelcontextprotocol/python-sdk/releases/tag/v1.30.0 (opens in a new tab)
- github.com/modelcontextprotocol/python-sdk/releases/tag/v2.2.0 (opens in a new tab)