Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-123800SuperTokens Core: App-scoped API key can overwrite the parent connection URI domain's credentials and take over sibling applications

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.

Timeline

  1. ID reserved

    By GitHub_M

  2. · 3 days later

    Published

  3. · 5 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-123800, by who scored it
Scored byCVSSScoreVector
GitHub_MCNA (assigner)3.1Critical9.9CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Deferred3.1Critical9.9CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.59% · top 51% of all CVEs (20 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.9.

Affected products

  • supertokens · supertokens-core

    • affected >= 6.0.0, < 6.0.24
    • affected >= 7.0.0, < 7.0.23
    • affected >= 8.0.0, < 8.0.7
    • affected >= 9.0.0, < 9.0.6
    • affected >= 9.1.0, < 9.1.6
    • affected >= 9.2.0, < 9.2.7
    • affected >= 9.3.0, < 9.3.5
    • affected >= 10.0.0, < 10.0.8
    • affected >= 10.1.0, < 10.1.9
    • affected >= 11.0.0, < 11.0.9
    • affected >= 11.1.0, < 11.1.4
    • affected >= 11.2.0, < 11.2.4
    • affected >= 11.3.0, < 11.3.8
    • affected >= 11.4.0, < 11.4.8
    • affected >= 12.0.0, < 12.0.11
    • affected >= 12.1.0, < 12.1.2
    • affected >= 12.2.0, < 12.2.1
    • affected >= 12.3.0, < 12.3.1

References

References37

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-123800 badge
[![CVE-2026-123800](https://cveledger.app/badge/CVE-2026-123800.svg)](https://cveledger.app/cve/CVE-2026-123800)

Record last updated .