Skip to main content
cve.nowby Sazabi
← Vulnerabilities
CVE-2026-123799EUVD-2026-120163

SuperTokens Core: Dashboard session tokens are never checked for expiry: `isValidUserSession` ignores the stored `expiry`, so a…

7.4HighCNA
Exploited
No known exploitation
Fix
Fixed in 11.0.9, 11.1.4, 11.2.4, 11.3.8, 11.4.8, and 2 more
Who is exposed
Not reported

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

Published
Last modified
25/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

SuperTokens Core, an open source authentication server, fails to check whether dashboard session tokens have expired, so an expired session still grants full dashboard read and write access. An attacker who already holds a dashboard administrator session can reach this remotely, without logging in, and keep using it after its 30-day lifetime until the session record is cleaned up.

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 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.

cve.now Index

25Pcve.now Index 25 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.4/10CVSS 7.4, total technical impact per CISA
  • No patch0/5No signal

What would change the score

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

How the score works · Rankings

What to do

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

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • supertokens supertokens-core

    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

Evidence 17

  1. Advisory
  2. Repository
  3. Repository
  4. Repository
  5. Repository
Show all 17 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

Corrections

None so far.

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

Questions about CVE-2026-123799

Is CVE-2026-123799 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-123799?

supertokens-core: 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.Source: cve.now feed data

How do I fix CVE-2026-123799?

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

Sources

CVSS details

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

Related

More vulnerabilities