Skip to content
Threat Brief

← All advisories

CVE-2026-119215

High 7.6No known exploitationFix available

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

Record last updated

CVSS score

7.6

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.5%

Higher than 44% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Weakness: CWE-639

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
Do 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. Source (opens in a new tab)
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
team-alembicash_authenticationfrom 5.0.0-rc.0 before 5.0.0-rc.165.0.0-rc.16CVE Program
team-alembicash_authenticationfrom 6e7a880698614887527a87df206b4eb0c0fbd8c1 before 4058be0f519c2e9b0d2266e90f9c7d8547d545744058be0f519c2e9b0d2266e90f9c7d8547d54574CVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references