CVE-2026-119215
AshAuthentication TOTP setup lets a user install their own authenticator secret on another user's account
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-119215 divulgada · CVSS 7.6 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: OSV | Registro visto por primera vez en OSV | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación ninguna | |
| Monitoreo | Fuente: ENISA EUVD | Registro visto por primera vez en ENISA EUVD | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
AshAuthentication, an Elixir authentication library used in applications built with the Ash framework, is affected: a user can install their own two-factor (TOTP) authenticator secret on another user's account. This lets an attacker sign in as the victim or hold the victim's second factor, and in some setups reveal the victim's pending setup secret.
Affects ash_authentication 5.0.0-rc.0 up to 5.0.0-rc.16 when TOTP setup or confirm_setup is exposed on a caller-chosen record with confirm_setup_enabled? set to true. Fixed in 5.0.0-rc.16.
Descripción original del registro (EEF)
Authorization Bypass Through User-Controlled Key vulnerability in team-alembic ash_authentication allows a user with an account to install a TOTP secret they control on another user's account, and then sign in as that user or hold their second factor. AshAuthentication.Strategy.Totp.ConfirmSetupChange verified a setup token but did not check that it was issued to the record being confirmed, so an attacker's own pending secret could be confirmed onto another user's record. The TOTP setup changes, ConfirmSetupChange, GeneratePendingSetupChange and GenerateSecretChange, also marked their changesets as AshAuthentication interactions, which the standard AshAuthenticationInteraction policy bypass lets through. A policy limiting setup and confirm_setup to the actor's own record therefore never ran when an application exposed those actions by record key, and a direct setup call on another user's record returned that user's pending secret and setup token. This issue affects ash_authentication: from 5.0.0-rc.0 before 5.0.0-rc.16.
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 |
|---|---|---|---|---|
ash_authentication |
Corregida | 5.0.0-rc.16 | — | — |
5.0.0-rc.16Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/team-alembic/ash_authentication/security/advisories/GHSA-gx67-694c-655chttps://github.com/team-alembic/ash_authentication/commit/4058be0f519c2e9b0d2266e90f9c7d8547d54574https://cna.erlef.org/cves/CVE-2026-119215.htmlhttps://osv.dev/vulnerability/EEF-CVE-2026-119215https://github.com/team-alembic/ash_authentication/commit/6e7a880698614887527a87df206b4eb0c0fbd8c1Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
