Answer in brief
CVE-2026-81632 records a Unknown severity vulnerability in Single-use sign-in token placed in a redirect query string in AshAuthenticationPhoenix. The current sources do not mark it as known exploited. The current feed maps team-alembic/ash_authentication (generic), team-alembic/ash_authentication (generic), team-alembic/ash_authentication_phoenix (generic), team-alembic/ash_authentication_phoenix (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps team-alembic/ash_authentication (generic), team-alembic/ash_authentication (generic), team-alembic/ash_authentication_phoenix (generic), team-alembic/ash_authentication_phoenix (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| team-alembic/ash_authenticationgeneric | >=3.10.5 <4.15.0 || >=5.0.0-rc.0 <5.0.0-rc.14 | 4.15.0, 5.0.0-rc.14 |
| team-alembic/ash_authenticationgeneric | >=eca8cadea0f1595ed2c10a0c177b1da9aa9e5269 <* | * |
| team-alembic/ash_authentication_phoenixgeneric | >=1.7.0 <2.17.4 || >=3.0.0-rc.0 <3.0.0-rc.11 | 2.17.4, 3.0.0-rc.11 |
| team-alembic/ash_authentication_phoenixgeneric | >=903f3a386e1aba2f7b070187ef6f31215a92bdfd <* | * |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.