Quick answers
- Is CVE-2026-119215 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119215 being exploited in the wild.
- How severe is CVE-2026-119215?
- Informational severity, published 3 November 2026.
- Which products and versions are affected?
- Team-Alembic Ash Authentication 5.0.0-rc.0 before 5.0.0-rc.16.
- Is there a fix for CVE-2026-119215?
- Yes: fixed in ash_authentication 5.0.0-rc.16. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119215 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-119215?
- Check whether you run Team-Alembic Ash Authentication at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: ash_authentication 5.0.0-rc.16
Technical details
The vulnerability exists in the TOTP (Time-based One-Time Password) setup flow, where ConfirmSetupChange verified a setup token but failed to validate it belonged to the target user's record. Additionally, the setup change operations were marked as AshAuthentication interactions, bypassing standard authorization policies that should restrict these actions to the actor's own record. An attacker could confirm their own pending TOTP secret on another user's account or retrieve another user's setup token by calling setup directly with that user's record key.
Affected products
- team-alembic ash_authentication 5.0.0-rc.0 before 5.0.0-rc.16
Timeline
- 2026-11-03: disclosed