llamaCVEVulnerability Intelligence
/
ash_authentication

CVE-2026-119215

AshAuthentication TOTP setup lets a user install their own authenticator secret on another user's account

Specific setups onlyParche disponibleinsecure direct object reference (IDOR)
Descargar PNG JSON
CVSS 4.0
7.6
Alta
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
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versión5.0.0-rc.16
Exposición16 dDesde la divulgación, 3 nov 2026, 10:46 a. m.
Detección6 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir de cerca
Monitorear y programar la remediación
Sin explotación conocida, no automatizable e impacto técnico total. Hay versiones corregidas disponibles.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +1
Modificada
Explotación
Remediación
Monitoreo
Detectada +3
Verificada
3 nov 26
19 nov 26
3 nov 26
7 nov 26
11 nov 26
15 nov 26
19 nov 26
FechaFaseEventoDetalle
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
Resumen
Resumen generado por IA · CC-BY 4.0

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.

¿Qué significa?An attacker can install their own TOTP secret on another user's account. That lets them sign in as the victim or hold the victim's second factor.
¿Quién está afectado?ash_authentication versions from 5.0.0-rc.0 before 5.0.0-rc.16 are in scope. The setup also needs the application to expose the TOTP setup or confirm_setup action on a record the caller identifies, the attacker to be able to read the victim's user record, and confirm_setup_enabled? set to true. To check a project, look at the ash_authentication version in mix.lock and the confirm_setup_enabled? setting in the TOTP strategy.
¿Qué hacer?Upgrade ash_authentication to 5.0.0-rc.16, which is the listed fixed version. No separate patch identifiers are named.
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.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
The application exposes the TOTP setup or confirm_setup action on a record the caller identifies, and the attacker can read the victim's user record.“Reachable when the application exposes the TOTP setup or confirm_setup action on a record the caller identifies, and the attacker can read the victim's user record”
02
Installing the attacker's secret requires confirm_setup_enabled? set to true.“Installing the attacker's secret requires confirm_setup_enabled? true”
¿Quién debe revisar?Teams running ash_authentication 5.0.0-rc.0 up to 5.0.0-rc.16 (excluded) that expose TOTP setup or confirm_setup on a record the caller chooses, e.g. via AshJsonApi or AshGraphql.
MitigaciónDo not expose setup or confirm_setup on a record the caller chooses. Call them through AshAuthentication.Strategy.Totp.Actions with the signed-in user instead.
Vector CVSS 4.0

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
Requisitos de ataqueAT:P
NingunoPresentes
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaPasivaActiva
Confid. (sistema)VC:H
AltoBajoNinguno
Integridad (sistema)VI:H
AltoBajoNinguno
Disponib. (sistema)VA:N
AltoBajoNinguno
Confid. (posterior)SC:N
AltoBajoNinguno
Integridad (posterior)SI:N
AltoBajoNinguno
Disponib. (posterior)SA:N
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
ash_authentication≥ 5.0.0-rc.0 < 5.0.0-rc.16
5.0.0-rc.0
5.0.0-rc.16
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
ash_authentication
Corregida 5.0.0-rc.16 — —
Versiones corregidas5.0.0-rc.16
Explotación

Arsenal público

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

Registro
EscenarioGENERALEEF
configurationAn application exposes the TOTP setup or confirm_setup action on a record the caller identifies, for example through AshJsonApi, AshGraphql or a controller that passes a looked-up user to AshAuthentication.Strategy.Totp.Actions.confirm_setup/3, and the attacker can read the victim's user record. Installing the attacker's secret requires confirm_setup_enabled? true; signing in with it alone requires sign_in_enabled? true. The routes AshAuthentication and AshAuthenticationPhoenix provide always use the signed-in user and are not affected.EEF
MitigaciónDo not expose setup or confirm_setup on a record the caller chooses. Call them through AshAuthentication.Strategy.Totp.Actions with the signed-in user, as the built-in routes do.EEF
Referencias
Fabricantehttps://github.com/team-alembic/ash_authentication/security/advisories/GHSA-gx67-694c-655c
Parchehttps://github.com/team-alembic/ash_authentication/commit/4058be0f519c2e9b0d2266e90f9c7d8547d54574
Otrahttps://cna.erlef.org/cves/CVE-2026-119215.html
Otrahttps://osv.dev/vulnerability/EEF-CVE-2026-119215
Otrahttps://github.com/team-alembic/ash_authentication/commit/6e7a880698614887527a87df206b4eb0c0fbd8c1

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