CyberSecBulletin
CVE-2026-81632NVD status: Deferred

ash_authentication_phoenix: Use of HTTP Request With Sensitive Query String

Published Updated By the CyberSecBulletin desk

CVE-2026-81632 is a high-severity use of HTTP request with sensitive query string vulnerability in ash_authentication_phoenix from Team-alembic, with a CVSS 4.0 base score of 7.2 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 2.17.4, 3.0.0-rc.11 as the first without the flaw, so updating ash_authentication_phoenix to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.21% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update ash_authentication_phoenix to 2.17.4 or 3.0.0-rc.11, whichever matches your release line, or a later version.
  2. Update ash_authentication to 4.15.0 or 5.0.0-rc.14, whichever matches your release line, or a later version.
  3. Read the advisory on github.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
Team-alembicash_authentication_phoenix1.7.0 up to, but not including, 2.17.4; 3.0.0-rc.0 up to, but not including, 3.0.0-rc.11; 903f3a386e1aba2f7b070187ef6f31215a92bdfd and later2.17.4, 3.0.0-rc.11
Team-alembicash_authentication3.10.5 up to, but not including, 4.15.0; 5.0.0-rc.0 up to, but not including, 5.0.0-rc.14; eca8cadea0f1595ed2c10a0c177b1da9aa9e5269 and later4.15.0, 5.0.0-rc.14

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Attack requirements
PresentThe target must be in a specific state or configuration for the attack to work.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Confidentiality (vulnerable system)
HighSerious loss of confidentiality on the vulnerable system.
Integrity (vulnerable system)
HighSerious loss of integrity on the vulnerable system.
Availability (vulnerable system)
NoneNo loss of availability on the vulnerable system.
Confidentiality (other systems)
NoneNo loss of confidentiality on systems beyond the vulnerable one.
Integrity (other systems)
NoneNo loss of integrity on systems beyond the vulnerable one.
Availability (other systems)
NoneNo loss of availability on systems beyond the vulnerable one.

Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. Scored by CNA.

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use of HTTP Request With Sensitive Query String

The web application uses an HTTP method to process a request, but the request includes sensitive information in the query string.

How developers prevent this class of flaw

  • When sending sensitive information, only include it in the request body or request headers instead of the query string. This may require avoiding use of GET requests.

More Use of HTTP Request With Sensitive Query String vulnerabilities (CWE-598)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in ash_authentication_phoenix

All ash_authentication_phoenix vulnerabilities

Recent Use of HTTP Request With Sensitive Query String vulnerabilities

Spotted an error? Tell us.