Skip to main content
veriom
Menu

Explore Veriom products, resources, and account pages.

CVE-2026-123799supertokens supertokens-core insufficient session expiration

Schedule itHigh7.4EPSS not scored yet

CVE-2026-123799 is a insufficient session expiration in supertokens supertokens-core, rated high (7.4 on CVSS 3.1).

Why this priority: High severity, with no exploitation signal yet.

Published · Updated · NVD status: Received

What it is

Sessions stay valid long after they should end.

How it is reached

An attacker can exploit it over the network, without an account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.

What an attacker gains

A successful attack can read the data it protects and change data or behaviour. In practice, this kind of flaw lets an attacker act as a signed-in user, or an administrator, without valid credentials.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade supertokens supertokens-core to a fixed version for your release line (11.0.9, 11.1.4, 11.2.4).
  2. Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Sign-in, session and token handling. The flaw sits between anonymous callers and authenticated sessions.
  • Identity providers and SSO. The flaw sits between anonymous callers and authenticated sessions.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
  • Between anonymous callers and authenticated sessions. An attacker who crosses it can act as a signed-in user, or an administrator, without valid credentials.

Questions to answer about your own systems

  • Where does supertokens supertokens-core run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?
See how Veriom maps an architectureTake the interactive tour

Read more

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.