CVE Watchtower

CVE-2026-119215team-alembic ash_authentication Authorization Bypass Through User-Controlled Key

NVD

Vulnerability Summary

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.
Severity Level
HIGH(7.6)
Published Date
Nov 3, 2026
Last Modified
Nov 19, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
0.51%Probability
Root Weakness (CWE)
The system does not prevent one user from accessing another user data or record by modifying the key value identifying the data.
CVSS v4.0 Base Metrics — Score 7.6 (HIGH)
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
Attack VectorNetwork
Attack ComplexityLow
Attack RequirementsPresent
Privileges RequiredLow
User InteractionNone
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)High
Availability (Vulnerable System)None
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None

Affected & Patched Versions

Affected Versions
  • team-alembic ash_authentication >= 5.0.0-rc.0 and < 5.0.0-rc.16
  • team-alembic ash_authentication >= 6e7a880698614887527a87df206b4eb0c0fbd8c1 and < 4058be0f519c2e9b0d2266e90f9c7d8547d54574
Patched Versions
  • team-alembic ash_authentication 5.0.0-rc.16
  • team-alembic ash_authentication 4058be0f519c2e9b0d2266e90f9c7d8547d54574

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is high.

  1. Check whether you run team-alembic ash_authentication and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Nov 3, 2026Published
  • Nov 19, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new team-alembic ash_authentication CVEsYou are reading CVE-2026-119215. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More team-alembic ash_authentication CVEs

Data last checked: Nov 19, 2026 13:08 UTC