HighCVE-2026-80218

    Sign-in token minted for one resource accepted by another in AshAuthentication (CVE-2026-80218)

    Published Last modified Sources: CVE.org, OSV

    Share

    What is affected, what to do

    Improper Authentication vulnerability in team-alembic AshAuthentication allows an attacker holding a sign-in token for one authenticated resource to be signed in as a user of a different resource. AshAuthentication.Strategy.Password.SignInWithTokenPreparation.extract_primary_keys_from_subject/2 parses the JWT sub claim (for example user?id=1) with URI.parse/1 and keeps only its query string, discarding the path segment that names the subject the token was issued for.

    Update Team-alembic Ash Authentication to version 4.15.0, Team-alembic Ash Authentication to version 5.0.0-rc.14.

    Affected
    • 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 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.6

    Priority

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

    Source: Vendor (CNA), CVSS v4

    7.6

    CVSS v4

    Severity High on the scale from 0 to 10.

    Source: CVE.org, OSV

    0.6 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 50.6

    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
    85.08 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.6 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.6
    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.6 %
    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
    50.6
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    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-287

    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

    Improper Authentication vulnerability in team-alembic AshAuthentication allows an attacker holding a sign-in token for one authenticated resource to be signed in as a user of a different resource. AshAuthentication.Strategy.Password.SignInWithTokenPreparation.extract_primary_keys_from_subject/2 parses the JWT sub claim (for example user?id=1) with URI.parse/1 and keeps only its query string, discarding the path segment that names the subject the token was issued for. Nothing else restores that binding: AshAuthentication.Jwt.verify/3 checks the signature, exp, nbf, jti and the library-version claims, the purpose check only requires sign_in, and the remaining comparison is over primary-key field names, which are identical across resources. The WebAuthn sign-in and remember-me preparations carry copies of the same helper and drop the path in the same way. The magic link sign-in path pins the subject name against the resource and is not affected. This issue affects ash_authentication: from 3.10.5 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.

    Source: cvelistv5, NVD (NIST), 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
    • 3.10.5 – < 4.15.0
    • 5.0.0-rc.0 – < 5.0.0-rc.14
    • 4.15.0
    • 5.0.0-rc.14
    hexash_authentication
    • 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
    • 5.0.0-rc.5
    • 4.7.2
    • 4.9.0
    • 4.6.4
    • 4.5.6
    • 4.3.2
    • 4.0.0-rc.5
    • 4.8.2
    • 5.0.0-rc.7
    • 5.0.0-rc.6
    • 4.3.7
    • 4.6.2
    • 4.8.7
    • 4.14.1
    • 4.6.3
    • 4.0.4
    • 3.11.11
    • 4.8.6
    • 4.9.1
    • 5.0.0-rc.3
    • 3.11.3
    • 3.11.14
    • 4.4.2
    • 3.12.1
    • 3.11.4
    • 4.2.0
    • 5.0.0-rc.4
    • 4.2.5
    • 4.13.7
    • 5.0.0-rc.12
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-287Improper Authentication

      Class

      When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

      Entry at MITRE CWE-287

    References & sources

    • github.comteam-alembic/ash_authentication/security/advisories/GHSA-3pr8-f…Vendor advisory, related
    • cna.erlef.orgEEF CNA record for CVE-2026-80218related
    • OSV (Open Source Vulnerabilities)OSV record EEF-CVE-2026-80218related
    • github.comIntroducing commit eca8cad in team-alembic/ash_authenticationrelated
    • github.comFix commit 2640e18 in team-alembic/ash_authenticationPatch
    • github.comFix commit 7baac24 in team-alembic/ash_authenticationPatch
    • 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-80218","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-17T18:28:40.896413Z"}

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

    2. ReceivedEEF

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

      Weakness type: CWE-287

      Description added or changed

      Show 10 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      Improper Authentication vulnerability in team-alembic AshAuthentication allows an attacker holding a sign-in token for one authenticated resource to be signed in as a user of a different resource. AshAuthentication.Strategy.Password.SignInWithTokenPreparation.extract_primary_keys_from_subject/2 parses the JWT sub claim (for example user?id=1) with URI.parse/1 and keeps only its query string, discarding the path segment that names the subject the token was issued for. Nothing else restores that binding: AshAuthentication.Jwt.verify/3 checks the signature, exp, nbf, jti and the library-version claims, the purpose check only requires sign_in, and the remaining comparison is over primary-key field names, which are identical across resources. The WebAuthn sign-in and remember-me preparations carry copies of the same helper and drop the path in the same way. The magic link sign-in path pins the subject name against the resource and is not affected. This issue affects 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:N/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-287
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80218.json">CVE-2026-80218</a>
      Referenceadded
      —
      https://cna.erlef.org/cves/CVE-2026-80218.html
      Referenceadded
      —
      https://github.com/team-alembic/ash_authentication/commit/2640e1872e1fef4e4606e601bf00102cff784c03
      Referenceadded
      —
      https://github.com/team-alembic/ash_authentication/commit/7baac243ca651eee127a84d672eee3fcff42e598
      Referenceadded
      —
      https://github.com/team-alembic/ash_authentication/commit/eca8cadea0f1595ed2c10a0c177b1da9aa9e5269
      Referenceadded
      —
      https://github.com/team-alembic/ash_authentication/security/advisories/GHSA-3pr8-f99q-86hp
      Referenceadded
      —
      https://osv.dev/vulnerability/EEF-CVE-2026-80218

      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-80218
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-80218"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-80218.svg?lang=en" alt="CVE-2026-80218 – NEOSEC Intel" height="20"></a>