llamaCVEVulnerability Intelligence
/
ash_authentication

CVE-2026-80218

Sign-in token minted for one resource accepted by another in AshAuthentication

Specific setups onlyParche disponibleauthentication bypass
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:09 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-80218 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

Improper Authentication vulnerability in team-alembic AshAuthentication allows an attacker holding a sign-in token for one authenticated resource to be signed in as a user of a different resource. AshAuthentication.Strategy.Password.SignInWithTokenPreparation.extract_primary_keys_from_subject/2 parses the JWT sub claim (for example user?id=1) with URI.parse/1 and keeps only its query string, discarding the path segment that names the subject the token was issued for. Nothing else restores that binding: AshAuthentication.Jwt.verify/3 checks the signature, exp, nbf, jti and the library-version claims, the purpose check only requires sign_in, and the remaining comparison is over primary-key field names, which are identical across resources. The WebAuthn sign-in and remember-me preparations carry copies of the same helper and drop the path in the same way. The magic link sign-in path pins the subject name against the resource and is not affected. This issue affects ash_authentication: from 3.10.5 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.

Affects ash_authentication 3.10.5 to before 4.15.0 and 5.0.0-rc.0 to before 5.0.0-rc.14, where sign-in tokens are enabled and two resources share a signing secret. Fixed in 4.15.0 and 5.0.0-rc.14.

¿Qué significa?A sign-in token issued for one authenticated resource can be accepted by another, so an attacker holding a valid token for one resource can obtain a session on another. This requires two authenticated resources that share a signing secret and a primary-key value present in both.
¿Quién está afectado?The bug is in ash_authentication from 3.10.5 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14. Check the ash_authentication version in your mix.lock, and whether sign_in_tokens_enabled? is set on your authenticated resources, since password sign-in with tokens requires it.
¿Qué hacer?Upgrade ash_authentication to 4.15.0 or 5.0.0-rc.14 or later. The advisory names no patch ids and no workaround.
Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Password sign-in with tokens requires sign_in_tokens_enabled?“Requires sign_in_tokens_enabled?”
02
Remember-me sign-in requires the remember_me strategy“Requires the remember_me strategy.”
03
WebAuthn sign-in requires the webauthn strategy (5.0 line only)“Requires the webauthn strategy”
04
Two authenticated resources sharing a signing secret, and a primary-key value present in both“Exploitation additionally requires two authenticated resources sharing a signing secret, and a primary-key value present in both.”
¿Quién debe revisar?Teams running ash_authentication 3.10.5 to 4.14.x or 5.0.0-rc.0 to 5.0.0-rc.13 with sign-in tokens, remember-me or WebAuthn across two or more authenticated resources sharing a signing secret.
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≥ 3.10.5 < 4.15.0
ash_authentication≥ 5.0.0-rc.0 < 5.0.0-rc.14
3.10.5
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-3pr8-f99q-86hp
Parchehttps://github.com/team-alembic/ash_authentication/commit/2640e1872e1fef4e4606e601bf00102cff784c03
Parchehttps://github.com/team-alembic/ash_authentication/commit/7baac243ca651eee127a84d672eee3fcff42e598
Otrahttps://cna.erlef.org/cves/CVE-2026-80218.html
Otrahttps://osv.dev/vulnerability/EEF-CVE-2026-80218
Otrahttps://github.com/team-alembic/ash_authentication/commit/eca8cadea0f1595ed2c10a0c177b1da9aa9e5269

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