llamaCVEVulnerability Intelligence
/
Python SDK

CVE-2026-115563

Python SDK credential leak in OAuth client authorization flow

A malicious server can capture client secrets, authorization codes, and signed assertions sent by the OAuth client.

UnclearParche disponiblemissing signature check
Descargar PNG JSON
CVSS 3.1
7.5
Alta
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Fuente: CNA
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche2 versionesPrimer parche a -70 d de la divulgación
Exposición3 dDesde la divulgación, 16 nov 2026, 3:24 p. m.
Detección4 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir
Remediar en la ventana regular de mantenimiento
Sin explotación conocida, automatizable e impacto técnico parcial. Hay versiones corregidas disponibles.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +2
Explotación
Remediación
Parche 1.30.0 +1
Monitoreo
Detectada +2
Fuente: OSV +1
7 sept 26
16 nov 26
19 nov 26
20 nov 26
7 sept 26
26 sept 26
14 oct 26
1 nov 26
20 nov 26
FechaFaseEventoDetalle
Remediación Parche 1.30.0 mcp · -70 d desde divulgación
Remediación Parche 2.2.0 mcp · -70 d desde divulgación
Divulgación Publicada CVE-2026-115563 divulgada · CVSS 7.5 (CNA)
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: NIST NVD Registro visto por primera vez en NIST NVD
Monitoreo Fuente: ENISA EUVD Registro visto por primera vez en ENISA EUVD
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Divulgación Modificada Última actualización del registro
Monitoreo Fuente: OSV Registro visto por primera vez en OSV
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 16 nov 2026

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.

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.

¿Qué significa?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.
¿Quién está afectado?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.
¿Qué hacer?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.
Descripción original del registro (GitHub_M)

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.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Uses the SDK as an MCP client over HTTP with one of the affected OAuth providers.“your application uses the SDK as an MCP client over HTTP with OAuthClientProvider”
02
Runs an affected version: 1.9.1 through 1.29.1 or 2.0.0 through 2.1.1.“1.9.1 through 1.29.1: no issuer check and no credential binding on any path.”
03
Holds credentials for a legitimate authorization server while possibly connecting to an MCP server that is not fully trusted.“it may connect to an MCP server you do not fully trust while holding credentials for a legitimate authorization server”
04
Not affected: MCP servers built with the SDK, stdio clients, and clients that attach their own tokens or headers.“clients that attach their own tokens or headers”
¿Quién debe revisar?Teams using the mcp Python SDK as HTTP MCP clients with OAuth providers, holding client credentials and possibly connecting to untrusted MCP servers.
No protegeUpgrading alone changes nothing for ClientCredentialsOAuthProvider or PrivateKeyJWTOAuthProvider; issuer= is also needed.
MitigaciónConnect OAuth-enabled clients only to MCP servers you trust (earlier versions).
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:N
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida Última
python-sdk · mcp≥ 1.9.1 < 1.30.0
python-sdk · mcp≥ 2.0.0a1 < 2.2.0
1.9.1
1.30.0
2.0.0a1
2.2.0
2.3.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
pypimcp
Corregida 1.30.0, 2.2.0 -70 d · -70 d 2.3.0 no afectada
Versiones corregidas1.30.02.2.0
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Fabricantehttps://github.com/modelcontextprotocol/python-sdk/security/advisories/GHSA-qx49-fqc8-xw99
Otrahttps://github.com/modelcontextprotocol/python-sdk/pull/3398
Otrahttps://github.com/modelcontextprotocol/python-sdk/pull/3431
Otrahttps://github.com/modelcontextprotocol/python-sdk/pull/3435
Otrahttps://github.com/modelcontextprotocol/python-sdk/commit/3eed7ce0a6aba76e8d94c4cfb9b266f41935392c
Otrahttps://github.com/modelcontextprotocol/python-sdk/commit/979208c1157661eac0151f90974a1f96528003fa
Otrahttps://github.com/modelcontextprotocol/python-sdk/commit/d060b36e1d095ef6e93e07ba5d59bb69b2ad449a
Otrahttps://github.com/modelcontextprotocol/python-sdk/releases/tag/v1.30.0
Otrahttps://github.com/modelcontextprotocol/python-sdk/releases/tag/v2.2.0

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.