Quick answers
- Is CVE-2026-123804 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123804 being exploited in the wild.
- How severe is CVE-2026-123804?
- Medium severity, with a CVSS score of 6.8, published 9 November 2026.
- Which products and versions are affected?
- Supertokens Core 7.0.0 until 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.
- Is there a fix for CVE-2026-123804?
- Yes: fixed in 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. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123804 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-123804?
- Check whether you run Supertokens Core at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 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 details
A race condition exists between session creation (createNewSession) and account unlinking (unlinkAccounts) where a session can be inserted after the primary user is resolved but before the unlink process revokes existing sessions. An attacker controlling a linked login method can exploit this timing window to maintain a valid, database-backed, refreshable session under the former primary identity. The vulnerability is a logic error in transaction serialization affecting versions 7.0.0 through 12.3.1.
Affected products
- SuperTokens Core 7.0.0 until 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
- 2026-11-09: disclosed