llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · @better-auth/sso

GHSA-MX9R-X6WW-QJW9

@better-auth/sso: Personal SSO providers can sign in as another provider's users

Parche disponible
Descargar PNG JSON
CVSS 3.1
8.1
Alta
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N Fuente: GitHub
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche2 versionesPrimer parche a -23 d de la divulgación
Exposición51 dDesde la divulgación, 29 sept 2026, 1:48 p. m.
Detección50 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Parche 1.7.3
Monitoreo
Detectada +1
6 sept 26
29 sept 26
18 nov 26
20 nov 26
6 sept 26
25 sept 26
13 oct 26
1 nov 26
20 nov 26
FechaFaseEventoDetalle
Remediación Parche 1.7.3 @better-auth/sso · -23 d desde divulgación
Divulgación Publicada GHSA-MX9R-X6WW-QJW9 divulgada · CVSS 8.1 (GitHub)
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

Am I affected?

You may be affected if you use `@better-auth/sso` `1.7.0-rc.2` through `1.7.0-rc.6` or `1.7.0` through `1.7.2`, and all of these conditions hold:

  • An attacker can register a personal SSO provider or use one they registered earlier. Registration is enabled by default for signed-in users, with a limit of 10 providers each.
  • Your application has not configured `resolveUser`.
  • A victim's account is linked through another OpenID Connect (OIDC) or SAML provider, and the attacker can reproduce that provider's identity and the victim's account identifier.

Configuring `resolveUser` requires an exact provider match and blocks this path. Setting `providersLimit: 0` only stops new registrations; existing providers remain usable.

Summary

The SSO plugin lets signed-in users register an OIDC or SAML provider. In affected versions, sign-in through a personal provider could match an account linked through a different provider and create a session for that account.

Impact

An attacker with a Better Auth account can register a provider that copies a real provider's identity and reproduces a victim's user identifier. Better Auth then creates a new session for the victim's account without victim interaction.

The attack does not compromise the real identity provider or steal the victim's existing session.

Patches

Upgrade `@better-auth/sso` to `1.7.3` or later. The fix prevents one provider from matching an account linked through another provider.

Workarounds

If you cannot upgrade now, block SSO sign-in at your application boundary until you can install the fixed release.

Setting `providersLimit: 0` prevents new personal-provider registration but does not disable providers that users already registered. If you keep SSO sign-in available, audit existing personal providers and remove any untrusted registrations. If you cannot verify that inventory, registration limits alone are only a partial mitigation.

If you already set `resolveUser`, the affected sign-in path requires an exact provider match. Upgrading is still the recommended fix.

Technical details

Affected versions found linked accounts by the provider's issuer (the OIDC issuer or SAML entity ID) and the account identifier from the sign-in (the OIDC subject or SAML NameID). The lookup did not also check that the account belonged to the `providerId` that handled the sign-in.

An attacker could register a personal provider with the same OIDC issuer or SAML entity ID as a legitimate provider. The attacker still controlled the new provider's endpoints or signing keys, so it could assert the subject or NameID of an account linked through the legitimate provider. Because the lookup did not enforce the `providerId` boundary, Better Auth treated the victim's account as belonging to the attacker's provider and created a session for the victim. The assertion was valid for the attacker's provider, but it did not prove control of the legitimate provider's account namespace.

Version `1.7.3` restores account lookup using both the registered `providerId` and the asserted account identifier.

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:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida Última
@better-auth/sso≥ 1.7.0-rc.2 < 1.7.0
@better-auth/sso≥ 1.7.0 < 1.7.3
1.7.0-rc.2
1.7.0
1.7.3
1.7.25
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npm@better-auth/sso
Corregida 1.7.3 -23 d 1.7.25 no afectada
Versiones corregidas1.7.01.7.3
Explotación

Arsenal público

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

Referencias
Advisoryhttps://github.com/better-auth/better-auth/security/advisories/GHSA-mx9r-x6ww-qjw9

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