CVE-2026-123804 · Package
NO FIX YET · SEE WHAT TO DO
SuperTokens Core is an open source authentication server. A race between session creation and account unlinking can leave a session alive as the former primary identity after a linked login method is removed, and that session persists until expiry or explicit revocation.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams that run a self-hosted SuperTokens Core server on affected versions from 7.0.0 up to the fixed releases, and that use account linking and unlinking in their login flows. An attacker needs to control a login method that is linked to a primary user. Deployments on other versions or those that do not link and unlink accounts are less exposed.
Not affected if default-config, managed-hosting
Who cares authentication, self-hosted, supertokens
unlinkAccounts calls in your application code that detach login methods from primary users.11.0.9, 11.1.4, 11.2.4, 11.3.8, 11.4.8, 12.0.11, , or , matching your release line.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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
12.1.212.2.112.3.1NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.