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

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0050, the 43rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

1. 3 Nov 2026, 15:46 UTC Confirmed by the CVE List
2. 3 Nov 2026, 15:53 UTC First seen by agentprime
3. 3 Nov 2026, 16:00 UTC Confirmed by OSV
4. 3 Nov 2026, 16:17 UTC Confirmed by NVD

Sources

• GitHub Advisory Database: GHSA-gx67-694c-655c
• OSV: GHSA-gx67-694c-655c
• github.com/team-alembic/ash_authentication/security/advisories/GHSA-gx67-694c-655c
• cna.erlef.org/cves/CVE-2026-119215.html
• github.com/team-alembic/ash_authentication/commit/6e7a880698614887527a87df206b4eb0c0fbd8c1
• github.com/team-alembic/ash_authentication/commit/4058be0f519c2e9b0d2266e90f9c7d8547d54574
• hex.pm/packages/ash_authentication

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.