CVE-2026-81632

Single-use sign-in token placed in a redirect query string in AshAuthenticationPhoenix

HIGH
7.2
CVSS Score
Published: September 17, 2026 at 01:09 PM UTC
Updated: September 18, 2026 at 06:29 PM UTC
2 products affected across 1 vendorAsh AuthenticationAsh Authentication Phoenix

Using ash_authentication_phoenix by team-alembic?

Get instant alerts when new vulnerabilities affect ash_authentication_phoenix - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.2
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

Use of HTTP Request With Sensitive Query String vulnerability in team-alembic AshAuthenticationPhoenix allows someone able to read access logs, proxy logs or browser history to recover a single-use sign-in token and authenticate as its owner. After a successful password sign-in, AshAuthentication.Phoenix.Components.Password.SignInForm builds the sign_in_with_token path with the freshly issued user.__metadata__.token as a query parameter and redirects the browser to it with a GET. The token therefore travels in the request line, where web servers, reverse proxies, request telemetry and the browser's own history record it, all of which outlive the request and are ordinarily less protected than session storage. The redirect destination is restricted to a local path, so this is not an open redirect; the exposure is the retention of a live credential. This issue affects ash_authentication_phoenix: from 1.7.0 before 2.17.4 and from 3.0.0-rc.0 before 3.0.0-rc.11; ash_authentication: from 3.10.5 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.10.5 ≤ v < 4.15.05.0.0-rc.0 ≤ v < 5.0.0-rc.143.10.55.0.0-rc.0eca8cadea0f1595ed2c10a0c177b1da9aa9e5269
Affected range stops below 4.15.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.0.0-rc.14, so it looks safe — our inference, not a vendor statement
1.7.0 ≤ v < 2.17.43.0.0-rc.0 ≤ v < 3.0.0-rc.111.7.03.0.0-rc.0903f3a386e1aba2f7b070187ef6f31215a92bdfd
Affected range stops below 2.17.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.0-rc.11, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.2HIGHEEF
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-598

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card