CVE-2026-123799 PUBLISHED

SuperTokens Core: Dashboard session tokens are never checked for expiry: `isValidUserSession` ignores the stored `expiry`, so a long-expired admin session still authenticates

Assigner: GitHub_M
Reserved: 06.11.2026 Published: 09.11.2026 Updated: 09.11.2026

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.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS Score: 7.4

Product Status

Vendor supertokens
Product supertokens-core
Versions
  • Version >= 11.0.0, < 11.0.9 is affected
  • Version >= 11.1.0, < 11.1.4 is affected
  • Version >= 11.2.0, < 11.2.4 is affected
  • Version >= 11.3.0, < 11.3.8 is affected
  • Version >= 11.4.0, < 11.4.8 is affected
  • Version >= 12.0.0, < 12.0.11 is affected
  • Version >= 12.1.0, < 12.1.2 is affected

References

Problem Types

  • CWE-613: Insufficient Session Expiration CWE