PoC Monitor
← All CVEs
CVE-2026-119215published 3 Nov 2026 15:46 UTCData: JSON · API

Team-alembic ash_authentication

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

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.6high · scored by CNA · CWE-639
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

team-alembic ash_authentication
  • >= 5.0.0-rc.0, < 5.0.0-rc.16

Fixed in 5.0.0-rc.16

team-alembic ash_authentication
  • >= 6e7a880698614887527a87df206b4eb0c0fbd8c1, < 4058be0f519c2e9b0d2266e90f9c7d8547d54574

Fixed in 4058be0f519c2e9b0d2266e90f9c7d8547d54574

Mitigation

Upgrade ash_authentication to 5.0.0-rc.16 or later.

Upgrade ash_authentication to 4058be0f519c2e9b0d2266e90f9c7d8547d54574 or later.

Workaround

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.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published3 Nov 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.