---
id: "CVE-2026-123800"
page: "https://infrastack.ai/live/CVE-2026-123800"
kind: "vulnerability"
aliases: ["CVE-2026-123800"]
title: "SuperTokens Core: tenant permission check lets an API key takeover sibling apps"
severity: "critical"
cvss: 9.9
epss: null
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["authentication", "multi-tenant", "other", "self-hosted", "supertokens"]
not_affected_if: ["default-config", "managed-hosting", "single-tenant"]
published_at: "2026-11-09T19:16:46+00:00"
first_seen_at: "2026-11-09T19:28:14+00:00"
updated_at: "2026-11-09T19:29:24+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-123800", "first_seen_at": "2026-11-09T19:28:14+00:00"}]
exploit_sources: []
---

# SuperTokens Core: tenant permission check lets an API key takeover sibling apps

Link for people: https://infrastack.ai/live/CVE-2026-123800 (this .md is for agents)

SuperTokens Core is an open source authentication server. In licensed multi-tenant deployments, a holder of one application's valid API key can update the parent connection URI domain and replace API keys, reading or modifying sibling users and obtaining their sessions.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed SuperTokens Core version against the fixed versions listed in the sources.
- Check whether the deployment runs a licensed multi-tenant setup with multiple applications under one non-default connection URI domain and separate api_keys.

## Fix

- Upgrade to a fixed version for 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`.

## Timeline

- 2026-11-09T19:28:14+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-123800

## Documents

- [fix] Patch: github.com https://github.com/supertokens/supertokens-core/commit/13c3de170dd40dd217db0f6bd2bded0948476a42
- [fix] Patch: github.com https://github.com/supertokens/supertokens-core/commit/1cc02b971f064c2fa2d9bc74b9e85795fdc6a7e5
- [fix] Patch: github.com https://github.com/supertokens/supertokens-core/commit/1d9dcb03ce0691d9b8abee48f86cc2729a6008cb
- [fix] Patch: github.com https://github.com/supertokens/supertokens-core/commit/337bb3eba812a5ee52d57854701820a0580b6050
- [fix] Patch: github.com https://github.com/supertokens/supertokens-core/commit/4902b713f31306ca41148070d10b6185f0e85201
- [fix] Patch: github.com https://github.com/supertokens/supertokens-core/commit/4d1ef0e177681f4f74995e4a25a17d224effe115
- [fix] Patch: github.com https://github.com/supertokens/supertokens-core/commit/61bfd3ebde1cf4b092da85ee884fa15e288aad51
- [fix] Patch: github.com https://github.com/supertokens/supertokens-core/commit/64dfa92c50a2ec288fe787ee5c2fad45548a6475
- [fix] Patch: github.com https://github.com/supertokens/supertokens-core/commit/8db9b0c39f97f240e116821434d4eb3c907faccf
- [fix] Patch: github.com https://github.com/supertokens/supertokens-core/commit/8e48ef856becbaaeb50ad4c915be1d7ce279416b
- [fix] Patch: github.com https://github.com/supertokens/supertokens-core/commit/9b0d3a9fdbdcb48dd7dd9d520075bbefbae3cf9b
- [fix] Patch: github.com https://github.com/supertokens/supertokens-core/commit/a186f1013c784de8a796a732e925e1870fec0f40

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_