Modelcontextprotocol Python-sdk: Insufficient Verification of Data Authenticity (CVE-2026-115563)
Published Last modified Sources: EUVD, OSV, Hersteller, CVE.org
What is affected, what to do
Update mcp to version 2.2.0.
- Affected
- Modelcontextprotocol Python-sdk
gte 1.9.1, < 1.30.0..*
- Modelcontextprotocol Python-sdk
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
7.5
XIEM Effective CVSS
Highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
7.5
CVSS v3
Severity High on the scale from 0 to 10.
Source: EUVD, OSV, Hersteller, CVE.org
0.3 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 25.7
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 72.78 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 7.5 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 7.5
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.3 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 25.7
- Elevated — this CVE ranks above at least 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · automatable · Technical impact: partial
- Source: CISA Vulnrichment, as of 16 November 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-345, CWE-522
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
Summary
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:
- the authorization server metadata
issuerwas not validated on every discovery path, and - stored or pre-provisioned client credentials were not bound to the authorization server they belong to.
A malicious or compromised MCP server could therefore direct them to a token endpoint of its choosing:
- by naming its own authorization server in its protected resource metadata, or
- by publishing none and serving metadata that presents the user's real authorization server as the
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).
Am I affected?
Yes, if both of these hold:
- your application uses the SDK as an MCP client over HTTP with
OAuthClientProvider,ClientCredentialsOAuthProvider,PrivateKeyJWTOAuthProvideror the deprecated 1.xRFC7523OAuthClientProvideras the transport'sauthhandler; - it may connect to an MCP server you do not fully trust while holding credentials for a legitimate authorization server (a pre-provisioned secret or signing key, or a stored client registration).
Affected versions:
- 1.9.1 through 1.29.1: no
issuercheck and no credential binding on any path. - 2.0.0 through 2.1.1: both missing whenever the server publishes no protected resource metadata (the legacy fallback) or answers
403 insufficient_scope. - Both lines, on every path:
ClientCredentialsOAuthProviderandPrivateKeyJWTOAuthProviderhad no way to name the authorization server their credentials belong to.
Not affected:
- MCP servers built with the SDK
- stdio clients
- clients that attach their own tokens or headers
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).
Fix
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"):
- Without it they still follow whichever authorization server the MCP server advertises.
- Omitting it now emits a deprecation warning, and it becomes required in 3.0. On 1.30.0 it is a
DeprecationWarning, which Python hides by default. - The deprecated 1.x
RFC7523OAuthClientProviderhas noissueroption. Move to one of these two providers.
In the fixed versions the client also:
- works out which issuer it expects before fetching any authorization server metadata, on every path;
- refuses metadata whose
issuerdiffers, withOAuthFlowError; - binds stored registrations to that issuer, and discards one bound to a different issuer so the client registers again.
After upgrading:
- Stored registrations: a registration stored without an issuer stays unbound. That includes everything 1.x stored before 1.30.0. Clear stored OAuth client information once so the client registers again. If you placed a pre-registered client in storage yourself, set
issueron that record instead. - Past exposure: if such a client may have connected to an untrusted MCP server, rotate its client secret and revoke its tokens at the authorization server.
On earlier versions there is no workaround other than connecting OAuth-enabled clients only to MCP servers you trust.
Source: ENISA EUVD, OSV (Open Source Vulnerabilities), GitHub Security Advisories, cvelistv5, NVD (NIST), CVE.org (MITRE)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| modelcontextprotocol | python-sdk |
|
|
| pip | mcp |
|
|
| pypi | mcp |
|
|
Vendors and products
Weakness classes (CWE)
CWE-345Insufficient Verification of Data Authenticity
Class
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
Entry at MITRE CWE-345CWE-522Insufficiently Protected Credentials
Class
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
Entry at MITRE CWE-522
References & sources
- github.commodelcontextprotocol/python-sdk/security/advisories/GHSA-qx49-f…euvd, x_refsource_CONFIRM, web
- github.commodelcontextprotocol/python-sdk/pull/3398euvd, x_refsource_MISC, web
- github.commodelcontextprotocol/python-sdk/pull/3431euvd, x_refsource_MISC, web
- github.commodelcontextprotocol/python-sdk/pull/3435euvd, x_refsource_MISC, web
- github.commodelcontextprotocol/python-sdk/commit/3eed7ce0a6aba76e8d94c4cf…euvd, x_refsource_MISC, web
- github.commodelcontextprotocol/python-sdk/commit/979208c1157661eac0151f90…euvd, x_refsource_MISC, web
- github.commodelcontextprotocol/python-sdk/commit/d060b36e1d095ef6e93e07ba…euvd, x_refsource_MISC, web
- github.commodelcontextprotocol/python-sdk/releases/tag/v1.30.0euvd, x_refsource_MISC, web
- github.commodelcontextprotocol/python-sdk/releases/tag/v2.2.0euvd, x_refsource_MISC, web
- NVD (NIST)vuln/detail/CVE-2026-115563advisory, euvd
- github.commodelcontextprotocol/python-sdkpackage
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: yes
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-115563","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-11-16T21:27:19.653024Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
ReceivedGitHub
CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weakness type: CWE-345, CWE-522
Description added or changed
New references:- https://github.com/modelcontextprotocol/python-sdk/commit/3eed7ce0a6aba76e8d94c4cfb9b266f41935392c
- https://github.com/modelcontextprotocol/python-sdk/commit/979208c1157661eac0151f90974a1f96528003fa
- https://github.com/modelcontextprotocol/python-sdk/commit/d060b36e1d095ef6e93e07ba5d59bb69b2ad449a
- https://github.com/modelcontextprotocol/python-sdk/pull/3398
and 5 more references
Show 14 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —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.CVSS added —AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NWeakness type (CWE) added —CWE-345Weakness type (CWE) added —CWE-522Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/115xxx/CVE-2026-115563.json">CVE-2026-115563</a>Reference added —https://github.com/modelcontextprotocol/python-sdk/commit/3eed7ce0a6aba76e8d94c4cfb9b266f41935392cReference added —https://github.com/modelcontextprotocol/python-sdk/commit/979208c1157661eac0151f90974a1f96528003faReference added —https://github.com/modelcontextprotocol/python-sdk/commit/d060b36e1d095ef6e93e07ba5d59bb69b2ad449aReference added —https://github.com/modelcontextprotocol/python-sdk/pull/3398Reference added —https://github.com/modelcontextprotocol/python-sdk/pull/3431Reference added —https://github.com/modelcontextprotocol/python-sdk/pull/3435Reference added —https://github.com/modelcontextprotocol/python-sdk/releases/tag/v1.30.0Reference added —https://github.com/modelcontextprotocol/python-sdk/releases/tag/v2.2.0Reference added —https://github.com/modelcontextprotocol/python-sdk/security/advisories/GHSA-qx49-fqc8-xw99Source identifier: security-advisories@github.com
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-115563"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-115563.svg?lang=en" alt="CVE-2026-115563 – NEOSEC Intel" height="20"></a>