team-alembic ash_authentication up to 5.0.0-rc.15 Totp Strategy authorization

Summaryinfo

A vulnerability was found in team-alembic ash_authentication up to 5.0.0-rc.15 and classified as critical. This issue affects the function AshAuthentication.Strategy.Totp.ConfirmSetupChange of the component Totp Strategy. The manipulation results in authorization. This vulnerability is cataloged as CVE-2026-119215. The attack may be launched remotely. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in team-alembic ash_authentication up to 5.0.0-rc.15. Affected is the function AshAuthentication.Strategy.Totp.ConfirmSetupChange of the component Totp Strategy. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is available at github.com. This vulnerability is traded as CVE-2026-119215 since 11/03/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. Technical details are known, but there is no available exploit.

Upgrading to version 5.0.0-rc.16 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• team-alembic

Name

• ash_authentication

Version

• 5.0.0-rc.0
• 5.0.0-rc.1
• 5.0.0-rc.2
• 5.0.0-rc.3
• 5.0.0-rc.4
• 5.0.0-rc.5
• 5.0.0-rc.6
• 5.0.0-rc.7
• 5.0.0-rc.8
• 5.0.0-rc.9
• 5.0.0-rc.10
• 5.0.0-rc.11
• 5.0.0-rc.12
• 5.0.0-rc.13
• 5.0.0-rc.14
• 5.0.0-rc.15

Website

• Product: https://github.com/team-alembic/ash_authentication/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion