Skip to main content
Menu
CVEs

CVE

Python SDK credential leak in OAuth client authorization flow

Affects MCP Python SDK clients 1.9.1 through 1.29.1 and 2.0.0 through 2.1.1 that use OAuthClientProvider over HTTP. Fixed in 1.30.0 and 2.2.0.

CVE-2026-115563EUVD-2026-126629

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.30.0, 2.2.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 1.30.0, 2.2.0.

Published
Last modified
Reference
Last checked
28/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

The Model Context Protocol Python SDK's OAuth client support can send a client secret, authorization code, PKCE code verifier, or signed client assertion to an authorization server chosen by an untrusted MCP server. An attacker can reach this remotely over the network, without logging in or any user action, by controlling the MCP server that HTTP clients connect to.

Original description

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.

Who should check

Teams using the mcp Python SDK as HTTP MCP clients with OAuth providers, holding client credentials and possibly connecting to untrusted MCP servers.

Not fixed by: Upgrading alone changes nothing for ClientCredentialsOAuthProvider or PrivateKeyJWTOAuthProvider; issuer= is also needed.

“1.9.1 through 1.29.1: no issuer check and no credential binding on any path.”

github.com

cve.now Index

28Pcve.now Index 28 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 33 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 1.30.0, 2.2.0.

  • Workaround: Connect OAuth-enabled clients only to MCP servers you trust (earlier versions).

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-115563 (Model Context Protocol Python SDK: OAuth client could send credentials to an authorization server chosen by the MCP server), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-115563 (entry last updated 2026-11-16):
Affected:
- modelcontextprotocol python-sdk: from 1.9.1, fixed in 1.30.0; from 2.0.0a1, fixed in 2.2.0
Fixed versions: 1.30.0, 2.2.0.
Conditions (all must be true for the bug to be hit):
- Uses the SDK as an MCP client over HTTP with one of the affected OAuth providers. (source: https://github.com/modelcontextprotocol/python-sdk/security/advisories/GHSA-qx49-fqc8-xw99)
- Runs an affected version: 1.9.1 through 1.29.1 or 2.0.0 through 2.1.1. (source: https://github.com/modelcontextprotocol/python-sdk/security/advisories/GHSA-qx49-fqc8-xw99)
- Holds credentials for a legitimate authorization server while possibly connecting to an MCP server that is not fully trusted. (source: https://github.com/modelcontextprotocol/python-sdk/security/advisories/GHSA-qx49-fqc8-xw99)
- Not affected: MCP servers built with the SDK, stdio clients, and clients that attach their own tokens or headers. (source: https://github.com/modelcontextprotocol/python-sdk/security/advisories/GHSA-qx49-fqc8-xw99)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Connect OAuth-enabled clients only to MCP servers you trust (earlier versions). (source: https://github.com/modelcontextprotocol/python-sdk/security/advisories/GHSA-qx49-fqc8-xw99)
CISA KEV: CVE-2026-115563 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-115563 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/modelcontextprotocol/python-sdk/security/advisories/GHSA-qx49-fqc8-xw99
- https://github.com/modelcontextprotocol/python-sdk/pull/3398
- https://github.com/modelcontextprotocol/python-sdk/pull/3431
- https://github.com/modelcontextprotocol/python-sdk/pull/3435
- 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/releases/tag/v1.30.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-115563
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-115563"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • modelcontextprotocol python-sdk

    From 1.9.1 · fixed in 1.30.0; From 2.0.0a1 · fixed in 2.2.0

Evidence 11

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 8

  1. Repository
  2. Repository
  3. Repository
  4. Repository
  5. Repository
  6. Repository
  7. Repository
  8. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-115563

Is CVE-2026-115563 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

An OAuth client built with the SDK can send its credentials to an authorization server chosen by the MCP server it connects to, rather than only to the legitimate server. A malicious or compromised MCP server could then receive the client_secret, authorization code, PKCE code_verifier, or signed client assertion meant for the real authorization server.Source: github.com

Which versions are affected by CVE-2026-115563?

python-sdk: from 1.9.1 before 1.30.0; from 2.0.0a1 before 2.2.0.Source: cve.now feed data

Am I affected, and how do I check?

Versions 1.9.1 through 1.29.1 and 2.0.0 through 2.1.1 of the MCP Python SDK are affected when the client uses OAuthClientProvider over HTTP and may connect to an MCP server that is not fully trusted while holding credentials for a legitimate authorization server. MCP servers built with the SDK, stdio clients, and clients that attach their own tokens or headers are not affected; check the installed SDK version with pip show mcp.Source: github.com

How do I fix CVE-2026-115563?

Upgrade to 1.30.0 or later on the 1.x line, or to 2.2.0 or later on the 2.x line. Upgrading is the only fix listed; the advisory names no patch identifiers.Source: github.com