HighCVE-2026-123802

    Supertokens-core: Insufficient Granularity of Access Control (CVE-2026-123802)

    Published Last modified Sources: CVE.org, EUVD

    Share

    What is affected, what to do

    SuperTokens Core is an open source authentication server. From 11.3.0 until 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, and 12.3.1, a licensed deployment with a configured SAML client can authenticate an identity from an assertion that did not satisfy the audience check.

    The available sources name no fixed version. Check the vendor guidance in the references below.

    Affected
    • Supertokens-core gte 11.3.0, < 11.3.8..*

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

    Metrics

    8.1

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    8.1

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org, EUVD

    0.3 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 23.0

    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
    74.74 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
    8.1 Methodology
    CVSS v3

    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
    8.1
    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.3 %
    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
    23.0
    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 13 November 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, CWE-345, CWE-1220

    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

    SuperTokens Core is an open source authentication server. From 11.3.0 until 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, and 12.3.1, a licensed deployment with a configured SAML client can authenticate an identity from an assertion that did not satisfy the audience check. When the identity provider uses assertion-level signing, an attacker who has a still-valid IdP-signed assertion naming the victim for any audience and the attacker's own valid assertion for the target audience can combine them because validateSamlResponseAudience accepts an audience from one assertion while extractAllClaims takes the final NameID and attributes from another; response-level signing does not expose this multi-assertion variant. Independently, an assertion from an identity provider configured for the target deployment but issued to another SuperTokens deployment using the shared default saml_sp_entity_id can satisfy the target's audience check. Successful exploitation authenticates the attacker as the victim IdP user. This issue is fixed in versions 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, and 12.3.1.

    Source: cvelistv5, NVD (NIST), ENISA EUVD

    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
    supertokenssupertokens-core
    • ≥ 11.3.0, < 11.3.8
    • —

    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
    • CWE-345Insufficient Verification of Data Authenticity

      Class

      The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

      Entry at MITRE CWE-345
    • CWE-1220Insufficient Granularity of Access Control

      Base

      The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets.

      Entry at MITRE CWE-1220

    References & sources

    • github.comsupertokens/supertokens-core/commit/00a15e045323ba8a566ca6f59b7…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/1645915320c5dfc22bce9029eb7…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/1d0fd5b40848629295cf86d47be…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/324686349b21ab46fe465ca5f74…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/53f42f496477e7cc3ccd48fe578…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/5ffdd887b470035f409d61f85f2…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/8e69a85e38709b832869c3bfc83…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/a2483b692d43294fdb9ad2f8f6f…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/b21760ceb5089b0fa30c8fd46f7…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/c77b13061176d9bd50ed24a9cf5…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/f4ddc022ef1ee17933efb710c21…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/releases/tag/v11.3.8x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/releases/tag/v11.4.8x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/releases/tag/v12.0.11x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/releases/tag/v12.1.2x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/releases/tag/v12.2.1x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/releases/tag/v12.3.1x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/security/advisories/GHSA-wfg2-vqfg…x_refsource_CONFIRM, euvd

    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-123802","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-11-13T12:34:58.126841Z"}

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

    2. ReceivedGitHub

      Show 24 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      SuperTokens Core is an open source authentication server. From 11.3.0 until 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, and 12.3.1, a licensed deployment with a configured SAML client can authenticate an identity from an assertion that did not satisfy the audience check. When the identity provider uses assertion-level signing, an attacker who has a still-valid IdP-signed assertion naming the victim for any audience and the attacker's own valid assertion for the target audience can combine them because validateSamlResponseAudience accepts an audience from one assertion while extractAllClaims takes the final NameID and attributes from another; response-level signing does not expose this multi-assertion variant. Independently, an assertion from an identity provider configured for the target deployment but issued to another SuperTokens deployment using the shared default saml_sp_entity_id can satisfy the target's audience check. Successful exploitation authenticates the attacker as the victim IdP user. This issue is fixed in versions 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, and 12.3.1.
      CVSSadded
      —
      AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
      Weakness type (CWE)added
      —
      CWE-287
      Weakness type (CWE)added
      —
      CWE-345
      Weakness type (CWE)added
      —
      CWE-1220
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/123xxx/CVE-2026-123802.json">CVE-2026-123802</a>
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/00a15e045323ba8a566ca6f59b70125b4030ab6c
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/1645915320c5dfc22bce9029eb7d8364f8df402f
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/1d0fd5b40848629295cf86d47be185f92f31e445
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/324686349b21ab46fe465ca5f74294d6c68d3859
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/53f42f496477e7cc3ccd48fe57851fa08d06a248
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/5ffdd887b470035f409d61f85f2186381ad9cdd6
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/8e69a85e38709b832869c3bfc83df9a150d6f3cf
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/a2483b692d43294fdb9ad2f8f6f831cca8300081
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/b21760ceb5089b0fa30c8fd46f7bbfc680de56dd
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/c77b13061176d9bd50ed24a9cf50ffbcdf332ee5
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/f4ddc022ef1ee17933efb710c21a960cb4ada083
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v11.3.8
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v11.4.8
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v12.0.11
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v12.1.2
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v12.2.1
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v12.3.1
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/security/advisories/GHSA-wfg2-vqfg-rqh6

      Source identifier: security-advisories@github.com

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