Not a U.S. government website. NDD is an independent vulnerability database by Volerion and is not affiliated with or endorsed by NIST or NVD.
VOLERION
Volerion Security Research

NOT DEFERRED DATABASE

VULNERABILITIES

CVE-2026-82685 Details

ANALYZED


This CVE record has been analyzed and enriched by NVDAPI.com as an independent party.

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.

Metrics

CVSS 3.x Severity and Vector Strings:

References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.

Weakness Enumeration

CWE-IDCWE NameSource
CWE-639Authorization Bypass Through User-Controlled KeyEEF

Affected Products

ProductVersions
team-alembic AshAuthentication
>= 0.5.0, <= 4.14.2 (semver)
>= 5.0.0-rc.0, <= 5.0.0-rc.13 (semver)

CPE

  • No CPEs found in CPE dictionary for this product.

Remediation

  • Upgrade: 4.15.0moderate effort
  • Upgrade: 5.0.0-rc.14moderate effort
  • Mitigation:low effort

    Do not expose the generated <code>:confirm</code> action on a caller-supplied record id. Route confirmation through <code>Confirmation.Actions.confirm/3</code>, the confirmation plug, or <code>ash_authentication_phoenix</code>'s <code>confirm_route</code>, all of which derive the record from the token.

  • Mitigation:low effort

    If the action is already exposed through AshGraphql or AshJsonApi, remove that exposure rather than relying on policies — the <code>AshAuthenticationInteraction</code> bypass means update policies will not stop the attack.

  • Mitigation:low effort

    A strict read policy on the user resource is a partial defence, because the framework API must load the target record first. Do not rely on it alone.

Change History

3 change records found show changes


QUICK INFO

CVE Dictionary Entry:
CVE-2026-82685
NVD Published Date:
Sep 17, 2026
NVD Last Modified:
Nov 20, 2026
Source:
EEF
CVE-2026-82685 Details - Not Deferred