GHSA-8jh5-339h-mqx9 — ash_authentication_phoenix
Fix: team-alembic/ash_authentication_phoenix@920257dGHSA-8jh5-339h-mqx9 is a CWE-598 vulnerability in ash_authentication_phoenix. A fix is available for ash_authentication_phoenix — see the affected versions and patch details below.
Single-use sign-in token placed in a redirect query string in AshAuthenticationPhoenix
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-8jh5-339h-mqx9.
Real-World Exposure
ash_authentication_phoenix💧ash_authenticationReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Hex packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💧Hex | ash_authentication_phoenix | ≥ 1.7.0&&< 2.17.4 | 2.17.4mix deps.update ash_authentication_phoenix |
| 💧Hex | ash_authentication | ≥ 3.10.5&&< 4.15.0 | 4.15.0mix deps.update ash_authentication |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ash_authentication_phoenix, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ash_authentication_phoenix to 2.17.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8jh5-339h-mqx9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8jh5-339h-mqx9 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-8jh5-339h-mqx9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-8jh5-339h-mqx9 in your dependencies?
O3 Security finds GHSA-8jh5-339h-mqx9 across Hex dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.