# CVE-2026-115563 — modelcontextprotocol python-sdk

> As of 2026-11-16, CVE-2026-115563 is a HIGH-severity vulnerability in modelcontextprotocol python-sdk, CVSS v3.1 7.5, EPSS 0.3% (25.5th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-115563 as of 2026-11-16; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-11-16

## What is CVE-2026-115563?

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.

The record classifies CVE-2026-115563 under weakness classes [CWE-345](https://intel.threadlinqs.com/cwe/CWE-345), [CWE-522](https://intel.threadlinqs.com/cwe/CWE-522). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 3 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 7.5 — HIGH (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **EPSS (FIRST):** 0.3% probability of exploitation in the next 30 days, higher than 25.5% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4.8/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-11-16

## Is CVE-2026-115563 being exploited?

No public exploitation evidence for CVE-2026-115563 is recorded in the sources Threadlinqs tracks — CISA KEV, Exploit-DB, public proof-of-concept repositories and ProjectDiscovery Nuclei — as of 2026-11-16. That is an absence of evidence in those feeds, not a guarantee that the vulnerability is unexploited.

## Affected products and versions

- **modelcontextprotocol**: python-sdk

## How to fix CVE-2026-115563

No vendor patch reference has been recorded for CVE-2026-115563 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-115563

No threat campaign in the Threadlinqs corpus currently references CVE-2026-115563, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com](https://github.com/modelcontextprotocol/python-sdk/security/advisories/GHSA-qx49-fqc8-xw99)

**Other references**

- [github.com](https://github.com/modelcontextprotocol/python-sdk/pull/3398)
- [github.com (3431)](https://github.com/modelcontextprotocol/python-sdk/pull/3431)
- [github.com (3435)](https://github.com/modelcontextprotocol/python-sdk/pull/3435)
- [github.com (3eed7ce0a6aba76e8d94c4cfb9b266f41935392c)](https://github.com/modelcontextprotocol/python-sdk/commit/3eed7ce0a6aba76e8d94c4cfb9b266f41935392c)
- [github.com (979208c1157661eac0151f90974a1f96528003fa)](https://github.com/modelcontextprotocol/python-sdk/commit/979208c1157661eac0151f90974a1f96528003fa)

_Showing 6 of 9 recorded references._

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-115563
No Threadlinqs detection currently covers CVE-2026-115563; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
