SuperTokens Core accepts expired dashboard sessions
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-613.
Summary
SuperTokens Core from 11.0.0 before 11.0.9, 11.1.0 before 11.1.4, 11.2.0 before 11.2.4, 11.3.0 before 11.3.8, 11.4.0 before 11.4.8, 12.0.0 before 12.0.11, and 12.1.0 before 12.1.2 does not compare the stored expiry of dashboard sessions to the current time (CWE-613). An attacker who obtains a dashboard administrator session after its 30-day lifetime can keep using it with full dashboard read and write access until the periodic cleanup removes the session, and frequent Core restarts can prevent that cleanup from running.
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 11.0.0 until 11.0.9, 11.1.4, 11.2.4, 11.3.8, 11.4.8, 12.0.11, and 12.1.2, Dashboard.isValidUserSession treats any stored session row as valid without comparing DashboardSessionInfo.expiry to the current time. DashboardQueries.getSessionInfoWithSessionId also selects by app and session identifier without an expiry predicate, leaving the periodic DeleteExpiredDashboardSessions cleanup as the only expiration enforcement. An attacker who obtains a dashboard administrator session after its 30-day lifetime can continue using POST /recipe/dashboard/session/verify until the row is removed, and frequent Core restarts can prevent the 12-hour cleanup sweep from running. The stale session retains full dashboard read and write access, but the flaw does not provide a way to guess or acquire the random session identifier. This issue is fixed in versions 11.0.9, 11.1.4, 11.2.4, 11.3.8, 11.4.8, 12.0.11, and 12.1.2.
Why it matters now
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
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| supertokens | supertokens-core | 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 | 11.0.9, 11.1.4, 11.2.4, 11.3.8, 11.4.8, 12.0.11, 12.1.2 | Patch available | CNA |
- supertokens-core Vendorsupertokens Affected 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 Fixed in 11.0.9, 11.1.4, 11.2.4, 11.3.8, 11.4.8, 12.0.11, 12.1.2 Patch available CNA
Remediation
Upgrade supertokens-core to fixed version 11.0.9, 11.1.4, 11.2.4, 11.3.8, 11.4.8, 12.0.11, or 12.1.2 on the matching release line.
Written with Claude Haiku 5.5 from the sources below · 2026-11-09
- Fix · CNA supertokens-core (supertokens) Fixed in 11.0.9, 11.1.4, 11.2.4, 11.3.8, 11.4.8, 12.0.11, 12.1.2
Timeline
- 2026-11-09 Threatist record created from CVE-2026-123799
- 2026-11-09 CISA SSVC decision points changed
- 2026-11-09 Priority changed: MEDIUM → LOW
References
Other 17
- https://github.com/supertokens/supertokens-core/security/advisories/GHSA-w9fp-wv6g-pqv8
- https://github.com/supertokens/supertokens-core/pull/1409
- https://github.com/supertokens/supertokens-core/commit/0f4817152278b39fbf21b97c3795b4fc68c12c38
- https://github.com/supertokens/supertokens-core/commit/4b315b2382c8eec2cde28fbda113597bffad8da5
- https://github.com/supertokens/supertokens-core/commit/699d806b5fc77ee6343f8e48e0769dce8049b078
- https://github.com/supertokens/supertokens-core/commit/8906b840669b28b3af7367cf18870db0044d0d18
- https://github.com/supertokens/supertokens-core/commit/bd8eb93001cf814a8065e8f3cea755af267bc308
- https://github.com/supertokens/supertokens-core/commit/ced1c913d53641e5eb8108caef110e55348b5401
- https://github.com/supertokens/supertokens-core/commit/da0ec91d20ecbb68730741f8b0dec8c986b68877
- https://github.com/supertokens/supertokens-core/commit/e72793ec5bd925fd3b9ff19328043dc2a03201bd
- https://github.com/supertokens/supertokens-core/releases/tag/v11.0.9
- https://github.com/supertokens/supertokens-core/releases/tag/v11.1.4
- https://github.com/supertokens/supertokens-core/releases/tag/v11.2.4
- https://github.com/supertokens/supertokens-core/releases/tag/v11.3.8
- https://github.com/supertokens/supertokens-core/releases/tag/v11.4.8
- https://github.com/supertokens/supertokens-core/releases/tag/v12.0.11
- https://github.com/supertokens/supertokens-core/releases/tag/v12.1.2
More supertokens vulnerabilities
- TI-2026-28002 A lack of tenant separation in SuperTokens Inc. CVSS 3.1CRITICAL 9.6
- TI-2026-87196 SuperTokens Core app API key can overwrite parent domain credentials CVSS 3.1CRITICAL 9.9
- 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
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences