Skip to main content
CVE-2026-115563VulnerabilityPublished

Model Context Protocol Python SDK: OAuth client could send credentials to an authorization server chosen by the MCP

Affects mcpSource GCVE Database

0
Compare
Authoritative record:CVE-2026-115563· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 2.2.0 soon.

Data as of 19 Nov 2026, 23:23 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade mcp to 2.2.0; mcp to 1.30.0.

Affected software

ProductAffectedFixed in
PyPImcpAffected
  • >=2.0.0a1 <2.2.0
Fixed in
  • 2.2.0
PyPImcpAffected
  • >=1.9.1 <1.30.0
Fixed in
  • 1.30.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade the MCP Python SDK to version 1.30.0 or later (for 1.x) or 2.2.0 or later (for 2.x) to obtain the official fix. After upgrading, ensure that the 'issuer' parameter is set for ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider to bind credentials to the correct authorization server. Clear stored OAuth client registrations to force re-registration with the correct issuer binding. If the client may have connected to an untrusted MCP server, rotate client secrets and revoke tokens at the authorization server. There is no effective workaround on earlier versions other than connecting OAuth-enabled clients only to fully trusted MCP servers.

Description

The Model Context Protocol (MCP) Python SDK versions 1.9.1 through 1.29.1 and 2.0.0 through 2.1.1 contain a vulnerability in their OAuth client implementation. The SDK does not properly validate the authorization server issuer metadata and does not bind stored client credentials to a specific authorization server. This allows a malicious or compromised MCP server to redirect OAuth credentials to an attacker-controlled authorization server, potentially exposing client secrets and authorization codes. The issue affects OAuth clients using certain providers and connecting to untrusted MCP servers. Fixed in versions 1.30.0 and 2.2.0, the fix includes strict issuer validation and credential binding. Users should upgrade and rotate credentials if exposure is suspected.

References

Community reviews

Loading reviews…