CVE-2026-119215

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

  • High 7.6

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.

Key facts

Published
3 Nov 2026
Last changed
3 Nov 2026
Assigned by
EEF
EPSS
0.505% likely to be exploited in the next 30 days, higher than 43.726% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.6CVSS 4.0, Highfrom the CNA (EEF)CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

What to do

  • 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.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs (CNA impact statement)

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
team-alembicash_authentication
  • Default status: unaffected
  • 5.0.0-rc.0 up to but excluding 5.0.0-rc.16 (affected)
team-alembicash_authentication
  • Default status: unaffected
  • 6e7a880698614887527a87df206b4eb0c0fbd8c1 up to but excluding 4058be0f519c2e9b0d2266e90f9c7d8547d54574 (affected)

Timeline

  1. 3 Nov 2026 Published

Weakness

References