CVE Catalog

CVE-2026-81632

HighCVSS 7.2
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.16%

5th percentile - higher than 5% of all known CVEs

Summary

The "Use of HTTP Request With Sensitive Query String" vulnerability in AshAuthenticationPhoenix causes a single-use sign-in token to be passed as a query parameter in the URL during login redirect. The token can be exposed in server logs, browser history, etc.

Risk Assessment

Someone with access to logs or browser history could capture a valid sign-in token and impersonate the user, compromising session confidentiality.

Recommendation

Upgrade ash_authentication_phoenix to version 2.17.4 or later (for 2.x) and 3.0.0-rc.11 or later (for 3.0.0-rc) with the fix. Avoid passing tokens in query parameters.

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS