Live › vulnerability › CVE-2026-119215
ash_authentication is an Elixir authentication library for the Ash framework. A signed-in user can confirm their own TOTP secret onto another user's account, then sign in as that user or hold their second factor.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 16:21 UTC. All times on this page are UTC.
Applications built on ash_authentication 5.0.0-rc.0 up to but not including 5.0.0-rc.16 that use the TOTP strategy and expose setup or confirm_setup actions by record key are exposed. Applications that do not use TOTP, or that restrict these actions to the actor's own record, are less exposed, though the bypass flaw still applies to the TOTP changes themselves.
No product ranges from the sources yet.
ash_authentication in mix.lock and note the versionTotp strategy and whether setup or confirm_setup actions are exposed by record keyash_authentication from 5.0.0-rc.16 onward (fixed in that release, per the affected range given)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-119215")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.