CVE-2026-123799 json
SuperTokens Core: Dashboard session tokens are never checked for expiry: `isValidUserSession` ignores the stored `expiry`, so a long-expired admin session still authenticates
published 5h ago modified 1h ago also EUVD-2026-120163
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- github.com/supertokens/supertokens-core@0f48171 commit
- github.com/supertokens/supertokens-core@4b315b2 commit
- github.com/supertokens/supertokens-core@699d806 commit
- github.com/supertokens/supertokens-core@8906b84 commit
- github.com/supertokens/supertokens-core@bd8eb93 commit
- github.com/supertokens/supertokens-core@ced1c91 commit
- github.com/supertokens/supertokens-core@da0ec91 commit
- github.com/supertokens/supertokens-core@e72793e commit
- github.com/supertokens/supertokens-core#1409 pull request
- github.com/supertokens/supertokens-core/releases/tag/v11.0.9 release
Is CVE-2026-123799 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 1h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected products
- supertokens supertokens-core
Classification
- Weakness
-
- CWE-613 DEPRECATED: Insufficient Session Expiration
References
- github.com /supertokens/supertokens-core/pull/1409
- github.com /supertokens/supertokens-core/commit/0f4817152278b39fbf21b97c3795b4fc68c12c38
- github.com /supertokens/supertokens-core/commit/4b315b2382c8eec2cde28fbda113597bffad8da5
- github.com /supertokens/supertokens-core/commit/699d806b5fc77ee6343f8e48e0769dce8049b078
- github.com /supertokens/supertokens-core/commit/8906b840669b28b3af7367cf18870db0044d0d18
- github.com /supertokens/supertokens-core/commit/bd8eb93001cf814a8065e8f3cea755af267bc308
- github.com /supertokens/supertokens-core/commit/ced1c913d53641e5eb8108caef110e55348b5401
- github.com /supertokens/supertokens-core/commit/da0ec91d20ecbb68730741f8b0dec8c986b68877
- github.com /supertokens/supertokens-core/commit/e72793ec5bd925fd3b9ff19328043dc2a03201bd
- github.com /supertokens/supertokens-core/security/advisories/GHSA-w9fp-wv6g-pqv8
- github.com /supertokens/supertokens-core/releases/tag/v11.0.9
- github.com /supertokens/supertokens-core/releases/tag/v11.1.4
- github.com /supertokens/supertokens-core/releases/tag/v11.2.4
- github.com /supertokens/supertokens-core/releases/tag/v11.3.8
- github.com /supertokens/supertokens-core/releases/tag/v11.4.8
- github.com /supertokens/supertokens-core/releases/tag/v12.0.11
- github.com /supertokens/supertokens-core/releases/tag/v12.1.2
Sources
- CVE List CVE-2026-123799
- NVD CVE-2026-123799
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.