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.
CVE-2026-115563
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-11-19. A secondary CVSS source baseline 7.5; sources differ by 0.0.
Also known asEUVD-2026-126629 (ENISA EUVD) · GHSA-qx49-fqc8-xw99 (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHhigh confidence
- EG Risk
- 49EG Risk 49/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.3% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.3%
- EPSS %ILE
- 21st
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.3% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 16, 2026
Last Modified
November 16, 2026
Advisory Details (9)
Auto-updated Nov 16, 2026v2.2.0
Patch available: modelcontextprotocol/python-sdk v2.2.0
https://github.com/modelcontextprotocol/python-sdk/releases/tag/v2.2.0v1.30.0
Patch available: modelcontextprotocol/python-sdk v1.30.0
https://github.com/modelcontextprotocol/python-sdk/releases/tag/v1.30.0commit d060b36e1d09 (modelcontextprotocol/python-sdk)
Patch available: modelcontextprotocol/python-sdk v2.2.0 (contains commit d060b36e1d09)
https://github.com/modelcontextprotocol/python-sdk/commit/d060b36e1d095ef6e93e07ba5d59bb69b2ad449acommit 979208c11576 (modelcontextprotocol/python-sdk)
Patch available: modelcontextprotocol/python-sdk v2.2.0 (contains commit 979208c11576)
https://github.com/modelcontextprotocol/python-sdk/commit/979208c1157661eac0151f90974a1f96528003facommit 3eed7ce0a6ab (modelcontextprotocol/python-sdk)
Patch available: modelcontextprotocol/python-sdk v1.30.0 (contains commit 3eed7ce0a6ab)
https://github.com/modelcontextprotocol/python-sdk/commit/3eed7ce0a6aba76e8d94c4cfb9b266f41935392cDeprecate constructing the pre-provisioned OAuth clients without an issuer
Patch available: modelcontextprotocol/python-sdk v2.2.0 (PR #3435 merged 2026-09-04)
https://github.com/modelcontextprotocol/python-sdk/pull/3435[v1.x] Validate the authorization server metadata issuer on every discovery path
Patch available: modelcontextprotocol/python-sdk v1.30.0 (PR #3431 merged 2026-09-04)
https://github.com/modelcontextprotocol/python-sdk/pull/3431Validate the authorization server metadata issuer on every discovery path
Patch available: modelcontextprotocol/python-sdk v2.2.0 (PR #3398 merged 2026-09-02)
https://github.com/modelcontextprotocol/python-sdk/pull/3398OAuth client could send credentials to an authorization server chosen by the MCP server · Advisory · modelcontextprotocol/python-sdk · GitHub
https://github.com/modelcontextprotocol/python-sdk/security/advisories/GHSA-qx49-fqc8-xw99Vendor Advisories for CVE-2026-115563(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | mcp @ 2.2.0 (fixes >= 2.0.0a1, < 2.2.0) | — | ghsa |
| pip | mcp @ 1.30.0 (fixes >= 1.9.1, < 1.30.0) | — | ghsa |
These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-11-20 01:52 UTCEchelonGraph re-scored
- 2026-11-20 01:52 UTCGHSA enrichmentGHSA-qx49-fqc8-xw99 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-11-19 12:26 UTCOSV refresh
- 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-11-16 22:30 UTCEchelonGraph re-scored
- 2026-11-16 21:28 UTCEchelonGraph re-scored
- 2026-11-16 21:02 UTCENISA EUVD ID recordedEUVD-2026-126629 · Source: ENISA EUVD
- 2026-11-16 20:29 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
- 2026-11-16 20:28 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-115563?
When was the CVE record for CVE-2026-115563 published?
Is CVE-2026-115563 actively exploited?
What is the CVSS score of CVE-2026-115563?
How do I remediate CVE-2026-115563?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-115563
Is Your Infrastructure Affected by CVE-2026-115563?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.