HighCVE-2026-81632

    Single-use sign-in token placed in a redirect query string in AshAuthenticationPhoenix (CVE-2026-81632)

    Published Last modified Sources: CVE.org, OSV

    Share

    What is affected, what to do

    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.

    Update Team-alembic Ash Authentication Phoenix to version 2.17.4, Team-alembic Ash Authentication Phoenix to version 3.0.0-rc.11, Team-alembic Ash Authentication to version 4.15.0.

    Affected
    • Team-alembic Ash Authentication Phoenix lt 1.7.0..2.17.4
    • Team-alembic Ash Authentication Phoenix lt 3.0.0-rc.0..3.0.0-rc.11
    • Team-alembic Ash Authentication lt 3.10.5..4.15.0
    • Team-alembic Ash Authentication lt 5.0.0-rc.0..5.0.0-rc.14
    Fixed in
    • Team-alembic Ash Authentication Phoenix 2.17.4
    • Team-alembic Ash Authentication Phoenix 3.0.0-rc.11
    • Team-alembic Ash Authentication 4.15.0
    • Team-alembic Ash Authentication 5.0.0-rc.14

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.2

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v4

    7.2

    CVSS v4

    Severity High on the scale from 0 to 10.

    Source: CVE.org, OSV

    0.2 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 11.4

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    63.29 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.2 Methodology
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.2
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.2 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    11.4
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 17 September 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-598

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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: NVD (NIST), cvelistv5, OSV (Open Source Vulnerabilities)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    team-alembicash_authentication
    • 5.0.0-rc.0 – < 5.0.0-rc.14
    • 3.10.5 – < 4.15.0
    • 5.0.0-rc.14
    • 4.15.0
    team-alembicash_authentication_phoenix
    • 3.0.0-rc.0 – < 3.0.0-rc.11
    • 1.7.0 – < 2.17.4
    • 3.0.0-rc.11
    • 2.17.4
    hexash_authentication
    • 3.11.15
    • 4.13.3
    • 3.10.8
    • 4.9.4
    • 4.5.0
    • 3.12.3
    • 4.3.0
    • 3.11.12
    • 3.10.7
    • 4.7.4
    • 5.0.0-rc.2
    • 3.11.8
    • 4.0.0-rc.0
    • 4.3.10
    • 5.0.0-rc.11
    • 4.9.3
    • 4.5.4
    • 5.0.0-rc.1
    • 4.4.1
    • 4.2.1
    • 3.11.6
    • 4.4.6
    • 3.10.6
    • 4.8.0
    • 4.0.0-rc.3
    • 4.7.5
    • 4.7.0
    • 4.11.0
    • 4.13.2
    • 4.9.6
    • 4.3.5
    • 4.7.1
    • 4.2.2
    • 4.9.9
    • 4.14.2
    • 4.1.0
    • 4.3.3
    • 4.0.0-rc.1
    • 3.12.4
    • 4.2.7
    • 4.4.0
    • 4.0.0-rc.6
    • 4.4.9
    • 4.13.5
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-598Use of HTTP Request With Sensitive Query String

      Variant

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

      Entry at MITRE CWE-598

    References & sources

    • github.comteam-alembic/ash_authentication_phoenix/security/advisories/GHS…Vendor advisory, related
    • cna.erlef.orgEEF CNA record for CVE-2026-81632related
    • OSV (Open Source Vulnerabilities)OSV record EEF-CVE-2026-81632related
    • github.comteam-alembic/ash_authentication/security/advisories/GHSA-j726-5…Vendor advisory, related
    • github.comIntroducing commit 903f3a3 in team-alembic/ash_authentication_phoenixrelated
    • github.comFix commit 920257d in team-alembic/ash_authentication_phoenixPatch
    • github.comFix commit ff5ad87 in team-alembic/ash_authentication_phoenixPatch
    • github.comIntroducing commit eca8cad in team-alembic/ash_authenticationrelated
    • github.comFix commit bbf345c in team-alembic/ash_authenticationPatch
    • github.comFix commit 8d8ddd2 in team-alembic/ash_authenticationPatch
    • hex.pmpackages/ash_authentication_phoenixpackage
    • hex.pmpackages/ash_authenticationpackage

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-81632","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-17T18:29:05.558007Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. ReceivedEEF

      CVSS V4.0: AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

      Weakness type: CWE-598

      Description added or changed

      Show 14 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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.
      CVSSadded
      —
      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
      Weakness type (CWE)added
      —
      CWE-598
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/81xxx/CVE-2026-81632.json">CVE-2026-81632</a>
      Referenceadded
      —
      https://cna.erlef.org/cves/CVE-2026-81632.html
      Referenceadded
      —
      https://github.com/team-alembic/ash_authentication/commit/8d8ddd25c69b669a92a701af74bff42e1aada998
      Referenceadded
      —
      https://github.com/team-alembic/ash_authentication/commit/bbf345c1bb7aa28bce5dd856ac0ed2427f103859
      Referenceadded
      —
      https://github.com/team-alembic/ash_authentication/commit/eca8cadea0f1595ed2c10a0c177b1da9aa9e5269
      Referenceadded
      —
      https://github.com/team-alembic/ash_authentication/security/advisories/GHSA-j726-59hm-r46r
      Referenceadded
      —
      https://github.com/team-alembic/ash_authentication_phoenix/commit/903f3a386e1aba2f7b070187ef6f31215a92bdfd
      Referenceadded
      —
      https://github.com/team-alembic/ash_authentication_phoenix/commit/920257d0460b9c7cbb42a83d0888c10f4eeeb88a
      Referenceadded
      —
      https://github.com/team-alembic/ash_authentication_phoenix/commit/ff5ad8737748afed9cdfde3ec3a05b8a4702a742
      Referenceadded
      —
      https://github.com/team-alembic/ash_authentication_phoenix/security/advisories/GHSA-8jh5-339h-mqx9
      Referenceadded
      —
      https://osv.dev/vulnerability/EEF-CVE-2026-81632

      Source identifier: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-81632
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-81632"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-81632.svg?lang=en" alt="CVE-2026-81632 – NEOSEC Intel" height="20"></a>