llamaCVEVulnerability Intelligence
/
ash_authentication

CVE-2026-82685

Confirmation token accepted on any record in AshAuthentication

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
Parche2 versiones4.15.0 · 5.0.0-rc.14
Exposición63 dDesde la divulgación, 17 sept 2026, 8:08 a. m.
Detección60 dDesde 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
Verificada
17 sept 26
17 nov 26
19 nov 26
17 sept 26
3 oct 26
19 oct 26
3 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-82685 divulgada · CVSS 7.6 (CNA)
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Monitoreo Detectada Ingresó al índice
Divulgación Modificada Última actualización del registro
Monitoreo Verificada Última verificación contra las fuentes
Resumen

Authorization Bypass Through User-Controlled Key vulnerability in team-alembic AshAuthentication allows an authenticated attacker to overwrite and confirm another user's email address, and so take over that account. A confirmation token issued to one user is accepted on any other user's record. AshAuthentication.AddOn.Confirmation.ConfirmChange verifies the token's signature and its act claim, then applies the changes stored against that token to whichever record the changeset targets, never comparing the sub claim against changeset.data. An attacker who registers an account and changes their own email replays the resulting token against a victim's record id, writing in their own address with force_change_attributes/2 and stamping confirmed_at, after which an ordinary password reset yields the account. The library's own confirmation flow is unaffected, because AshAuthentication.AddOn.Confirmation.Actions.confirm/3 resolves sub to a user and targets that record. This issue affects ash_authentication: from 0.5.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.

Affects ash_authentication from 0.5.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14, where the generated confirm action is exposed on a caller-supplied record id. Fixed in 4.15.0 and 5.0.0-rc.14.

¿Qué significa?A confirmation token is accepted on any record, so an authenticated attacker can overwrite and confirm another user's email address. The attacker can then take over that account through a password reset.
¿Quién está afectado?Affected versions are ash_authentication from 0.5.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14. The setup also matters: the confirm update action must be exposed on a caller-supplied record id (for example through AshGraphql or AshJsonApi), and a read policy must let the requester load or reference the other user's record. Check the ash_authentication version in your mix.lock, and check whether the confirm action is exposed through AshGraphql or AshJsonApi.
¿Qué hacer?Upgrade ash_authentication to 4.15.0 or 5.0.0-rc.14, the fixed versions for each range. The advisory names no patch ids.
Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
The generated confirm update action is exposed on a caller-supplied record id (for example through AshGraphql or AshJsonApi), rather than only through the library's confirmation wrapper, plug or Phoenix route.“Both require the application to have exposed the confirm action on a caller-supplied record id.”
02
A read policy lets the attacker load or reference the victim's user record.“A read policy permitting the attacker to load or reference the victim record.”
03
ash_authentication from 0.5.0 before 4.15.0, or 5.0.0-rc.0 before 5.0.0-rc.14.“This issue affects ash_authentication: from 0.5.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.”
¿Quién debe revisar?Teams on ash_authentication from 0.5.0 to before 4.15.0, or 5.0.0-rc.0 to before 5.0.0-rc.14, that expose the confirm action on a caller-supplied record id, e.g. via AshGraphql or AshJsonApi.
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≥ 0.5.0 < 4.15.0
ash_authentication≥ 5.0.0-rc.0 < 5.0.0-rc.14
0.5.0
4.15.0
5.0.0-rc.0
5.0.0-rc.14
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
ash_authentication
Corregida 4.15.0, 5.0.0-rc.14 — —
Versiones corregidas4.15.05.0.0-rc.14
Explotación

Arsenal público

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

Registro
EscenarioGENERALEEF
Referencias
Fabricantehttps://github.com/team-alembic/ash_authentication/security/advisories/GHSA-g636-26vf-2w63
Parchehttps://github.com/team-alembic/ash_authentication/commit/d7c15c21d39c009206e010cd67e2d86370fe7a28
Parchehttps://github.com/team-alembic/ash_authentication/commit/2a2396af131ab67e2f445b805fecce8e6ca86c0e
Otrahttps://cna.erlef.org/cves/CVE-2026-82685.html
Otrahttps://osv.dev/vulnerability/EEF-CVE-2026-82685
Otrahttps://github.com/team-alembic/ash_authentication/commit/1d4bb00617aecae85c33f2ff5bc7e094c6449a6e

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