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

GHSA-9HM7-XHFP-CX58

better-auth: OAuth sign-in can treat an unverified provider email as verified

Parche disponible
Descargar PNG JSON
CVSS 3.1
5.9
Media
CVSS:3.1/AV:N/AC:H/PR:H/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 el mismo día de la divulgación
Exposición16 dDesde la divulgación, 3 nov 2026, 4:39 p. m.
Detección14 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.16 +1
Monitoreo
Detectada +1
3 nov 26
18 nov 26
20 nov 26
3 nov 26
8 nov 26
12 nov 26
16 nov 26
20 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-9HM7-XHFP-CX58 divulgada · CVSS 5.9 (GitHub)
Remediación Parche 1.7.16 better-auth · 0 d desde divulgación
Remediación Parche 1.8.0-beta.5 better-auth · 0 d desde divulgación
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 are affected if you use OAuth sign-in from `better-auth` 0.4.9 or later and any of these is true:

  • A provider sends `email_verified` as a string and lets its users keep an unverified address. Amazon Cognito's user info endpoint is one example.
  • You use `genericOAuth()` with a provider that has a JWKS endpoint.
  • You use the Zoom provider with `disableSignUp`, `requireEmailVerification`, or `overrideUserInfoOnSignIn`.

You are not affected for providers listed in `account.accountLinking.trustedProviders`, where linking by email is intended.

Summary

String claims. Better Auth treated any non-empty `email_verified` value as verified, so the string `"false"` passed.

Profile and token mismatch. With generic OAuth, the user info profile was not checked against the ID token's subject, and direct ID-token sign-in could load the profile from a submitted access token.

Zoom options. The Zoom provider ignored its configured provider options.

Impact

Someone who can hold another person's address unverified at an affected provider can sign in and be linked to the local account that owns it, and gets a session for that account. Accounts created this way are marked verified. A profile mismatch can attach a different provider identity than the one the ID token names. On Zoom, closed registration and email verification requirements did not apply.

Patches

Upgrade `better-auth` to 1.7.16, or to 1.8.0-beta.5 on the beta line.

An email now counts as verified only when the claim is `true` or the string `"true"`, including values returned from `mapProfileToUser`.

Workarounds

For a provider that sends string claims, provide a `getUserInfo` function that converts `email_verified` to a boolean. For Zoom, turn off the provider if you rely on the ignored options.

Technical details

The linking code tested `emailVerified` for truthiness when deciding whether an untrusted provider may link to an existing user and when storing the value for a new user. It now normalizes the claim at those points. Generic OAuth providers with a `jwks_uri` now reject a profile whose `sub` differs from the ID token, and ID-token sign-in ignores submitted access and refresh tokens. Direct ID-token sign-in already applied `disableSignUp` from 1.7.7. This release applies the Zoom provider's options the same way.

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:H
BajaAlta
PrivilegiosPR:H
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≥ 0.4.9 < 1.7.16
better-auth≥ 1.8.0-beta.0 < 1.8.0-beta.5
0.4.9
1.7.16
1.7.26
1.8.0-beta.0
1.8.0-beta.5
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npmbetter-auth
Corregida 1.7.16, 1.8.0-beta.5 0 d · 0 d 1.7.26 no afectada
Versiones corregidas1.7.161.8.0-beta.5
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-9hm7-xhfp-cx58

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