Skip to main content
← Vulnerabilities

SuperTokens Core: A session created concurrently with account unlink survives the unlink

6.8MediumCNA
Exploited
No known exploitation
Fix
Fixed in 11.0.0, 11.0.9, 11.1.4, 11.2.4, 11.3.8, and 5 more
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 11.0.0, 11.0.9, 11.1.4, 11.2.4, 11.3.8, or one of 5 more.

Published
Last modified
10/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

SuperTokens Core, an open source authentication server, has a race condition where a session created at the same moment an account is unlinked can survive the unlink. An attacker who controls a linked login method can reach this remotely with low privileges and keep a long-lived session as the former primary identity.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

SuperTokens Core is an open source authentication server. From 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, createNewSession can resolve a primary user before unlinkAccounts detaches a login method and then insert the session after unlink has enumerated and revoked the existing sessions. A user who controls the linked login method can exploit this race to retain a signed, database-backed, refreshable session as the former primary identity after that method is unlinked; the session persists until expiry or explicit revocation. This issue is fixed in versions 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.

cve.now Index

10Pcve.now Index 10 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.8/10CVSS 6.8
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 11.0.0, 11.0.9, 11.1.4, 11.2.4, 11.3.8, or one of 5 more.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • supertokens supertokens-core

    From 7.0.0 · fixed in 11.0.0; From 11.0.0 · fixed in 11.0.9; From 11.1.0 · fixed in 11.1.4; From 11.2.0 · fixed in 11.2.4; From 11.3.0 · fixed in 11.3.8; From 11.4.0 · fixed in 11.4.8; From 12.0.0 · fixed in 12.0.11; From 12.1.0 · fixed in 12.1.2; From 12.2.0 · fixed in 12.2.1; From 12.3.0 · fixed in 12.3.1

Evidence 21

  1. Advisory
  2. Repository
  3. Repository
  4. Repository
  5. Repository
Show all 21 sourcesShow fewer sources
  1. Repository
  2. Repository
  3. Repository
  4. Repository
  5. Repository
  6. Repository
  7. Repository
  8. Repository
  9. Repository
  10. Repository
  11. Repository
  12. Repository
  13. Repository
  14. Repository
  15. Repository
  16. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-123804

Is CVE-2026-123804 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-123804?

supertokens-core: from 7.0.0 before 11.0.0; from 11.0.0 before 11.0.9; from 11.1.0 before 11.1.4; from 11.2.0 before 11.2.4; from 11.3.0 before 11.3.8; from 11.4.0 before 11.4.8; from 12.0.0 before 12.0.11; from 12.1.0 before 12.1.2; from 12.2.0 before 12.2.1; from 12.3.0 before 12.3.1.Source: cve.now feed data

How do I fix CVE-2026-123804?

Upgrade to a fixed version: 11.0.0, 11.0.9, 11.1.4, 11.2.4, 11.3.8, or one of 5 more.Source: cve.now feed data