CVE-2026-82685: team-alembic ash_authentication · Insecure Direct Object Reference
Affects team-alembic ash_authenticationSource CVE Database V5
Not known to be exploited · CVSS 7.6 High : upgrade to 5.0.0-rc.14 or 4.15.0 soon.
Data as of 1 Nov 2026, 22:58 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.0.0-rc.14, 4.15.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.
What to do
Upgrade team-alembic ash_authentication to 5.0.0-rc.14 or 4.15.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| team-alembicash_authentication | Affected
| Fixed in
|
| team-alembicash_authentication | Affected
| Fixed in
|
| team-alembicash_authentication | Affected
| Fixed in– |
Hexash_authenticationpkg:hex/ash_authenticationOther threats | Affected
| Fixed in
|
CPE configurations (1)
cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, avoid using affected versions or implement additional authorization checks to ensure the token's subject matches the targeted user record during email confirmation.
Description
Authorization Bypass Through User-Controlled Key vulnerability in team-alembic AshAuthentication allows an authenticated attacker to overwrite and confirm another user's email address, and so take over that account. A confirmation token issued to one user is accepted on any other user's record. AshAuthentication.AddOn.Confirmation.ConfirmChange verifies the token's signature and its act claim, then applies the changes stored against that token to whichever record the changeset targets, never comparing the sub claim against changeset.data. An attacker who registers an account and changes their own email replays the resulting token against a victim's record id, writing in their own address with force_change_attributes/2 and stamping confirmed_at, after which an ordinary password reset yields the account. The library's own confirmation flow is unaffected, because AshAuthentication.AddOn.Confirmation.Actions.confirm/3 resolves sub to a user and targets that record. This issue affects ash_authentication: from 0.5.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.
References
- github.com/team-alembic/ash_authentication/security/advisories/GHSA-g636-26vf-2w63 (opens in a new tab)
- cna.erlef.org/cves/CVE-2026-82685.html (opens in a new tab)
- osv.dev/vulnerability/EEF-CVE-2026-82685 (opens in a new tab)
- github.com/team-alembic/ash_authentication/commit/1d4bb00617aecae85c33f2ff5bc7e094c6449a6e (opens in a new tab)
- github.com/team-alembic/ash_authentication/commit/d7c15c21d39c009206e010cd67e2d86370fe7a28 (opens in a new tab)
- github.com/team-alembic/ash_authentication/commit/2a2396af131ab67e2f445b805fecce8e6ca86c0e (opens in a new tab)