CriticalCVE-2026-123800

    Supertokens-core: Authorization Bypass Through User-Controlled Key (CVE-2026-123800)

    Published Last modified Sources: CVE.org, EUVD

    Share

    What is affected, what to do

    SuperTokens Core is an open source authentication server. From 6.0.0 until 6.0.24, 7.0.23, 8.0.7, 9.0.6, 9.1.6, 9.2.7, 9.3.5, 10.0.8, 10.1.9, 11.0.9, 11.1.4, 11.2.4, 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, and 12.3.1, Multitenancy.checkPermissionsForCreateOrUpdate in src/main/java/io/supertokens/multitenancy/Multitenancy.java does not adequately authorize updates to a parent connection URI domain or the base tenant.

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

    Affected
    • Supertokens-core gte 6.0.0, < 6.0.24..*

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

    Metrics

    9.9

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    9.9

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org, EUVD

    0.6 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 48.7

    Show all metrics
    Severity
    Critical
    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
    98.50 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
    9.9 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
    9.9
    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
    48.7
    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 14 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-639, CWE-863

    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 6.0.0 until 6.0.24, 7.0.23, 8.0.7, 9.0.6, 9.1.6, 9.2.7, 9.3.5, 10.0.8, 10.1.9, 11.0.9, 11.1.4, 11.2.4, 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, and 12.3.1, Multitenancy.checkPermissionsForCreateOrUpdate in src/main/java/io/supertokens/multitenancy/Multitenancy.java does not adequately authorize updates to a parent connection URI domain or the base tenant. In a licensed multi-tenant deployment with multiple applications under one non-default connection URI domain and separate api_keys, an attacker holding one application's valid API key can update the parent domain because the CUD-target branch checks the domain without requiring the source application and tenant to be public. Because api_keys is not protected, the attacker can replace the parent key and then sibling application keys, read or modify sibling users, obtain sessions as those users, establish persistence through a sibling dashboard user, and lock out the sibling application's own key. In the advisory's v2 create or update handlers, omitting the optional identifier produces a base-tenant target that skips the permission branches and enterprise-feature gate, allowing changes to firstFactors, required secondary factors, and recipe-enabled flags that affect login integrity and availability. The base-target variant still rejects coreConfig and does not establish key theft. This issue is fixed in versions 6.0.24, 7.0.23, 8.0.7, 9.0.6, 9.1.6, 9.2.7, 9.3.5, 10.0.8, 10.1.9, 11.0.9, 11.1.4, 11.2.4, 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
    • ≥ 6.0.0, < 6.0.24
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-639Authorization Bypass Through User-Controlled Key

      Base

      The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

      Entry at MITRE CWE-639
    • CWE-863Incorrect Authorization

      Class

      The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

      Entry at MITRE CWE-863

    References & sources

    • github.comsupertokens/supertokens-core/commit/13c3de170dd40dd217db0f6bd2b…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/1cc02b971f064c2fa2d9bc74b9e…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/1d9dcb03ce0691d9b8abee48f86…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/337bb3eba812a5ee52d57854701…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/4902b713f31306ca41148070d10…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/4d1ef0e177681f4f74995e4a25a…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/61bfd3ebde1cf4b092da85ee884…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/64dfa92c50a2ec288fe787ee5c2…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/8db9b0c39f97f240e116821434d…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/8e48ef856becbaaeb50ad4c915b…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/9b0d3a9fdbdcb48dd7dd9d52007…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/a186f1013c784de8a796a732e92…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/b58bc3d03549d20495df71c03ef…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/bf6184f027a99bd1b3b1df3d20e…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/c6d7dc7d73b9bb3075b3f7a1a0c…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/df79f3b4399ef31aea4cb44cc7b…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/e616f4002c31d256f9ff6cb3d36…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/commit/ff9ca3ec53861a91996c4e9581f…x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/releases/tag/v10.0.8x_refsource_MISC, euvd
    • github.comsupertokens/supertokens-core/releases/tag/v10.1.9x_refsource_MISC, 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-123800","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-11-14T01:50:19.086900Z"}

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

    2. ReceivedGitHub

      Show 42 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      SuperTokens Core is an open source authentication server. From 6.0.0 until 6.0.24, 7.0.23, 8.0.7, 9.0.6, 9.1.6, 9.2.7, 9.3.5, 10.0.8, 10.1.9, 11.0.9, 11.1.4, 11.2.4, 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, and 12.3.1, Multitenancy.checkPermissionsForCreateOrUpdate in src/main/java/io/supertokens/multitenancy/Multitenancy.java does not adequately authorize updates to a parent connection URI domain or the base tenant. In a licensed multi-tenant deployment with multiple applications under one non-default connection URI domain and separate api_keys, an attacker holding one application's valid API key can update the parent domain because the CUD-target branch checks the domain without requiring the source application and tenant to be public. Because api_keys is not protected, the attacker can replace the parent key and then sibling application keys, read or modify sibling users, obtain sessions as those users, establish persistence through a sibling dashboard user, and lock out the sibling application's own key. In the advisory's v2 create or update handlers, omitting the optional identifier produces a base-tenant target that skips the permission branches and enterprise-feature gate, allowing changes to firstFactors, required secondary factors, and recipe-enabled flags that affect login integrity and availability. The base-target variant still rejects coreConfig and does not establish key theft. This issue is fixed in versions 6.0.24, 7.0.23, 8.0.7, 9.0.6, 9.1.6, 9.2.7, 9.3.5, 10.0.8, 10.1.9, 11.0.9, 11.1.4, 11.2.4, 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:C/C:H/I:H/A:H
      Weakness type (CWE)added
      —
      CWE-639
      Weakness type (CWE)added
      —
      CWE-863
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/123xxx/CVE-2026-123800.json">CVE-2026-123800</a>
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/13c3de170dd40dd217db0f6bd2bded0948476a42
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/1cc02b971f064c2fa2d9bc74b9e85795fdc6a7e5
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/1d9dcb03ce0691d9b8abee48f86cc2729a6008cb
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/337bb3eba812a5ee52d57854701820a0580b6050
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/4902b713f31306ca41148070d10b6185f0e85201
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/4d1ef0e177681f4f74995e4a25a17d224effe115
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/61bfd3ebde1cf4b092da85ee884fa15e288aad51
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/64dfa92c50a2ec288fe787ee5c2fad45548a6475
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/8db9b0c39f97f240e116821434d4eb3c907faccf
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/8e48ef856becbaaeb50ad4c915be1d7ce279416b
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/9b0d3a9fdbdcb48dd7dd9d520075bbefbae3cf9b
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/a186f1013c784de8a796a732e925e1870fec0f40
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/b58bc3d03549d20495df71c03ef5478799c184db
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/bf6184f027a99bd1b3b1df3d20e376dda6521399
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/c6d7dc7d73b9bb3075b3f7a1a0c0c5780430c292
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/df79f3b4399ef31aea4cb44cc7b65761a2cb94a7
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/e616f4002c31d256f9ff6cb3d3685b924ef53a6d
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/commit/ff9ca3ec53861a91996c4e9581fa6f2e01331736
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v10.0.8
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v10.1.9
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v11.0.9
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v11.1.4
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v11.2.4
      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/releases/tag/v6.0.24
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v7.0.23
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v8.0.7
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v9.0.6
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v9.1.6
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v9.2.7
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/releases/tag/v9.3.5
      Referenceadded
      —
      https://github.com/supertokens/supertokens-core/security/advisories/GHSA-4rf2-xqvf-8rcx

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