Y2Y2
Explore more on Y2
Public vulnerability disclosure
Investigate in Cyber
Open

CVE-2026-123800

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

publishedCWE-639CWE-863

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.

Technical severity9.9 criticalCVSS 3.1 · CNA: GitHub_M
Published2026-11-09Source updated 2026-11-09
Collected2026-11-091 attributed source

Fixes and workarounds

No remediation reported in collected sources.

Missing remediation information is not evidence that no patch exists.

Affected products and versions

ProductVersionsAuthority
supertokens-core
supertokens 		>= 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 (affected) 		CNA: GitHub_M

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

Version / scoreVectorAuthority
3.1 / 9.9
critical		 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HCNA: GitHub_M

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Get an API keyUse x402Connect an agent
Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide