Read the docs

SuperTokens Core app API key can overwrite parent domain credentials

Priority MEDIUM 44CWE-639Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-639.

Summary

SuperTokens Core is affected from 6.0.0 before each release line's fixed version. In licensed multi-tenant deployments, an attacker with low privileges and one application's valid API key can overwrite the parent domain's api_keys (CWE-639). That lets the attacker read or modify sibling users, obtain their sessions and lock out sibling applications. Omitting the optional identifier in the v2 handlers also changes login settings.

Written with Claude Haiku 5.5 from the sources below · 2026-11-09

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00588 48th percentileScored 2026-11-16
Fix Fixed supertokens-core (supertokens): 6.0.24, 7.0.23, 8.0.7 +15

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
supertokenssupertokens-core6.0.0 to before 6.0.24; 7.0.0 to before 7.0.23; 8.0.0 to before 8.0.7; 9.0.0 to before 9.0.6; 9.1.0 to before 9.1.6; 9.2.0 to before 9.2.7; 9.3.0 to before 9.3.5; 10.0.0 to before 10.0.8; 10.1.0 to before 10.1.9; 11.0.0 to before 11.0.9; 11.1.0 to before 11.1.4; 11.2.0 to before 11.2.4; 11.3.0 to before 11.3.8; 11.4.0 to before 11.4.8; 12.0.0 to before 12.0.11; 12.1.0 to before 12.1.2; 12.2.0 to before 12.2.1; 12.3.0 to before 12.3.16.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, 12.3.1Patch availableCNA
  • supertokens-core Vendorsupertokens Affected 6.0.0 to before 6.0.24; 7.0.0 to before 7.0.23; 8.0.0 to before 8.0.7; 9.0.0 to before 9.0.6; 9.1.0 to before 9.1.6; 9.2.0 to before 9.2.7; 9.3.0 to before 9.3.5; 10.0.0 to before 10.0.8; 10.1.0 to before 10.1.9; 11.0.0 to before 11.0.9; 11.1.0 to before 11.1.4; 11.2.0 to before 11.2.4; 11.3.0 to before 11.3.8; 11.4.0 to before 11.4.8; 12.0.0 to before 12.0.11; 12.1.0 to before 12.1.2; 12.2.0 to before 12.2.1; 12.3.0 to before 12.3.1 Fixed in 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, 12.3.1 Patch available CNA

Remediation

Upgrade supertokens-core to the fixed version in your release line: 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 or 12.3.1.

Written with Claude Haiku 5.5 from the sources below · 2026-11-09

  • Fix · CNA supertokens-core (supertokens) Fixed in 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, 12.3.1

Timeline

  1. 2026-11-09 Threatist record created from CVE-2026-123800
  2. 2026-11-14 CISA SSVC decision points changed

References

Other 37

  • TI-2026-28002 A lack of tenant separation in SuperTokens Inc. CVSS 3.1CRITICAL 9.6
  • TI-2026-87188 Unknown tenant path bypasses API key enforcement in SuperTokens Core CVSS 3.1HIGH 7.5
  • TI-2026-87206 WebAuthn sign-in in SuperTokens Core accepts passkeys across tenants CVSS 3.1HIGH 8.1
  • TI-2026-87198 SuperTokens Core SAML lets attackers sign in as other IdP users CVSS 3.1HIGH 8.1
  • TI-2026-87194 SAML signature wrapping in SuperTokens Core lets users log in as others CVSS 3.1HIGH 8.1
  • TI-2026-87195 SuperTokens Core accepts expired dashboard sessions CVSS 3.1HIGH 7.4
See all 8 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences