# CVE-2026-123799: SuperTokens Core is an open source authentication server.


- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-w9fp-wv6g-pqv8

## What is CVE-2026-123799?

CVE-2026-123799 is a high-severity vulnerability in supertokens-core, published on 9 Nov 2026. 

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

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2026-123799?


## How do I fix CVE-2026-123799?

No fix has been published for CVE-2026-123799 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-123799 being exploited?

There is no known exploitation of CVE-2026-123799 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123799 and fix it if it is affected.

What it is: CVE-2026-123799 is a high-severity vulnerability in supertokens-core, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123799 in the wild and no public exploit code.

Affected product: supertokens-core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123799/ (Markdown: https://insights.sbomify.com/CVE-2026-123799/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123799
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123799
- OSV: https://osv.dev/vulnerability/CVE-2026-123799

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123799/
Summaries are generated and may contain mistakes; the official description above is the record.