llamaCVEVulnerability Intelligence
/
Advisory · GitHub · PyPI · mcp

GHSA-QX49-FQC8-XW99

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

Parche disponible
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: GitHub
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche2 versionesPrimer parche a -73 d de la divulgación
Exposición9 hDesde la divulgación, 19 nov 2026, 5:45 p. m.
Detección1 minDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +1
Explotación
Remediación
Parche 1.30.0 +1
Monitoreo
Detectada +3
7 sept 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 · -73 d desde divulgación
Remediación Parche 2.2.0 mcp · -73 d desde divulgación
Monitoreo Detectada Ingresó al índice
Divulgación Publicada GHSA-QX49-FQC8-XW99 divulgada · CVSS 7.5 (GitHub)
Divulgación Modificada Última actualización del registro
Monitoreo Fuente: GitHub Security Advisories Registro visto por primera vez en GitHub Security Advisories
Monitoreo Fuente: OSV Registro visto por primera vez en OSV
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

### Summary
In affected versions, the SDK's OAuth client support (`mcp.client.auth`) let the MCP server a client connected to decide where the client's OAuth credentials were sent:

  • the authorization server metadata `issuer` was not validated on every discovery path, and
  • stored or pre-provisioned client credentials were not bound to the authorization server they belong to.

A malicious or compromised MCP server could therefore direct them to a token endpoint of its choosing:

  • by naming its own authorization server in its protected resource metadata, or
  • by publishing none and serving metadata that presents the user's real authorization server as the `issuer`.

It would then receive the `client_secret`, authorization code and PKCE `code_verifier` meant for that real server (or, with `PrivateKeyJWTOAuthProvider`, a signed client assertion).

### Am I affected?
Yes, if both of these hold:

  • your application uses the SDK as an MCP client over HTTP with `OAuthClientProvider`, `ClientCredentialsOAuthProvider`, `PrivateKeyJWTOAuthProvider` or the deprecated 1.x `RFC7523OAuthClientProvider` as the transport's `auth` handler;
  • it may connect to an MCP server you do not fully trust while holding credentials for a legitimate authorization server (a pre-provisioned secret or signing key, or a stored client registration).

Affected versions:

  • 1.9.1 through 1.29.1: no `issuer` check and no credential binding on any path.
  • 2.0.0 through 2.1.1: both missing whenever the server publishes no protected resource metadata (the legacy fallback) or answers `403 insufficient_scope`.
  • Both lines, on every path: `ClientCredentialsOAuthProvider` and `PrivateKeyJWTOAuthProvider` had no way to name the authorization server their credentials belong to.

Not affected:

  • MCP servers built with the SDK
  • stdio clients
  • clients that attach their own tokens or headers

The rating is scored for the unattended providers. With the interactive `OAuthClientProvider` a person has to start the sign-in; scored that way it is 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`).

### Fix
Upgrade to `mcp` 2.2.0 (2.x) or 1.30.0 (1.x) or later.

If you use `ClientCredentialsOAuthProvider` or `PrivateKeyJWTOAuthProvider`, upgrading changes nothing until you also pass `issuer=` (for example `issuer="https://auth.example.com"`):

  • Without it they still follow whichever authorization server the MCP server advertises.
  • Omitting it now emits a deprecation warning, and it becomes required in 3.0. On 1.30.0 it is a `DeprecationWarning`, which Python hides by default.
  • The deprecated 1.x `RFC7523OAuthClientProvider` has no `issuer` option. Move to one of these two providers.

In the fixed versions the client also:

  • works out which issuer it expects before fetching any authorization server metadata, on every path;
  • refuses metadata whose `issuer` differs, with `OAuthFlowError`;
  • binds stored registrations to that issuer, and discards one bound to a different issuer so the client registers again.

After upgrading:

  • Stored registrations: a registration stored without an issuer stays unbound. That includes everything 1.x stored before 1.30.0. Clear stored OAuth client information once so the client registers again. If you placed a pre-registered client in storage yourself, set `issuer` on that record instead.
  • Past exposure: if such a client may have connected to an untrusted MCP server, rotate its client secret and revoke its tokens at the authorization server.

On earlier versions there is no workaround other than connecting OAuth-enabled clients only to MCP servers you trust.

Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · GitHub
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
mcp≥ 1.9.1 < 1.30.0
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 -73 d · -73 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
Advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-115563
Otrahttps://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
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.