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

Summary

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.

Timeline

1. Sep 17, 2026, 1:09 PM UTCCVE published
2. Sep 17, 2026, 6:29 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Sep 17, 2026, 6:29 PM UTCRecord last updated

Affected versions

• ash_authentication_phoenix

  From 1.7.0 · fixed in 2.17.4; From 3.0.0-rc.0 · fixed in 3.0.0-rc.11

• team-alembic/ash_authentication_phoenix

  Version range not reported

• ash_authentication

  From 3.10.5 · 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

References 10