CVE-2026-55216
Logto account takeover via social account linking
A remote attacker with a low-privilege login can link a social identity to a victim's account and sign in as them.
Texto original en inglés · Ver en español
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-55216 divulgada · CVSS 8.1 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Logto's social account linking in the standard OAuth 2.0 and Azure AD connectors can trust an unverified email address from the identity provider, letting an attacker with a low-privilege login link their own social identity to a victim's existing account and sign in as that victim. The attack can be carried out remotely over the network and needs no action from the victim.
Affects Logto when the OAuth 2.0 or Azure AD social connector is used with a provider that does not verify email addresses or lets users set email freely, and account linking is enabled. Fixed in 1.46.0.
Descripción original del registro (GitHub_M)
Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.46.0, social account linking can use an unverified email returned by the standard OAuth 2.0 or Azure AD connector to select an existing local account. When findSocialRelatedUser matches a victim's email and a request to POST /api/experience/identification enables linkSocialIdentity, an attacker who controls that unverified provider email can link an attacker-controlled social identity to the victim account and sign in as the victim. The issue applies when the provider does not verify email ownership or allows the value to be set freely; Google, GitHub, and default OIDC connector behavior is not affected because those paths expose only verified email. Version 1.46.0 adds an opt-in email synchronization control to the standard OAuth 2.0 connector, while the Azure AD connector has offered an equivalent opt-in control since version 1.43.0. These controls preserve existing behavior by default, so administrators must enable them on affected connectors. A configurable mitigation is available in version 1.46.0.
Condiciones y alcance
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
logto |
Corregida | 1.46.0 | — | — |
1.46.0Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/logto-io/logto/security/advisories/GHSA-gc94-xqg8-v8r7https://github.com/logto-io/logto/pull/9858https://github.com/logto-io/logto/commit/1b03993a59c627ae83f0c892d76988ca056208b0https://github.com/logto-io/logto/releases/tag/v1.46.0Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
