Read the docs
TI-2026-84395 Aliases CVE-2026-119215

TOTP setup in AshAuthentication lets users take over others' accounts

Priority LOW 36CWE-639Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-639.

Summary

team-alembic ash_authentication from 5.0.0-rc.0 before 5.0.0-rc.16 lets a user with an account install a TOTP secret they control on another user's account. AshAuthentication.Strategy.Totp.ConfirmSetupChange does not check that a setup token was issued to the record being confirmed (CWE-639). An attacker can then sign in as that user or hold their second factor, and the setup changes skip the actor-scoped policy when an application exposes them by record key.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00505 43rd percentileScored 2026-11-07
Fix Fixed ash_authentication (team-alembic): 5.0.0-rc.16

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
team-alembicash_authentication5.0.0-rc.0 to before 5.0.0-rc.165.0.0-rc.16Patch availableCNA
  • ash_authentication Vendorteam-alembic Affected 5.0.0-rc.0 to before 5.0.0-rc.16 Fixed in 5.0.0-rc.16 Patch available CNA

CPE names CNA · 1

CPEVersionsRoleVendor
cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*———
  • cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:* Versions — — ·—

Remediation

Upgrade ash_authentication to 5.0.0-rc.16 or later, which fixes the flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

  • Fix · CNA ash_authentication (team-alembic) Fixed in 5.0.0-rc.16

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    team-alembic ash_authentication 5.0.0-rc.16

    2 records Highest priority Priority LOW 2 LOW

    Other records, highest priority first

    • TI-2026-84394 Missing sign-in attempt limit in AshAuthentication custom actionsPriority LOW 29
    Show all 2 records →

Timeline

  1. 2026-11-03 Threatist record created from CVE-2026-119215
  2. 2026-11-03 CISA SSVC decision points changed
  3. 2026-11-03 Priority changed: MEDIUM → LOW

References

Patch 1

Advisory 1

Other 3

  • TI-2026-36668 OAuth2/OIDC account takeover in AshAuthentication via email-based user matching CVSS 4.0CRITICAL 9.2
  • TI-2026-46782 Purpose-limited JWT accepted as full bearer authentication in AshAuthentication CVSS 4.0HIGH 7.6
  • TI-2026-59214 Revoked session accepted because the session jti is never checked in AshAuthentication and AshAuthentication Phoenix CVSS 4.0CRITICAL 9.1
  • TI-2026-58664 `require_confirmed_with` is not enforced on the action and fails open on an unreadable attribute in AshAuthentication CVSS 4.0CRITICAL 9.1
  • TI-2026-53751 Remember-me sign-in guard reads a session key that is never written in ash_authentication, allowing session replacement CVSS 4.0CRITICAL 9.1
  • TI-2026-57079 Magic link single-use tokens replayable via TOCTOU race in AshAuthentication CVSS 4.0CRITICAL 9.1
See all 23 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences