VulnerabilityPublished 9 Nov 2026

CVE-2026-123797: supertokens-core · Authentication Bypass Using an Alternate Path or Channel

Affects supertokens-coreSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High · fixed in 12.0.8 : patch supertokens-core soon.

Data as of 9 Nov 2026, 18:04 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	7.5

Patch: Available – fixed in 12.0.8, 11.4.6, 11.3.6

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade supertokens-core to 12.0.8, 11.4.6 or 11.3.6.

Affected software

Product	Affected	Fixed in
supertokenssupertokens-core	Affected >=12.0.6 <12.0.8	Fixed in 12.0.8
supertokenssupertokens-core	Affected >=11.4.0 <11.4.6	Fixed in 11.4.6
supertokenssupertokens-core	Affected <11.3.6	Fixed in 11.3.6

AI-suggested

Upgrade SuperTokens Core to version 11.3.6, 11.4.6, or 12.0.8 or later, as these versions contain the official fixes for this vulnerability. No other mitigations are indicated by the vendor advisory.

Description

CVE-2026-123797 is an authentication bypass vulnerability in SuperTokens Core, an open source authentication server. Versions before 11.3.6, between 11.4.0 and 11.4.6, and between 12.0.6 and 12.0.8 are affected. The flaw allows unauthenticated attackers to bypass API-key and public-tenant enforcement by exploiting app-specific management requests using an unknown tenant path and an older supported CDI version. This enables unauthorized creation and enumeration of application roles via specific API endpoints. The issue is fixed in versions 11.3.6, 11.4.6, and 12.0.8.

Impact

An unauthenticated attacker can bypass authentication controls to create and enumerate application roles without a valid API key. This compromises the integrity of role management within the affected SuperTokens Core server, potentially allowing unauthorized privilege escalation or unauthorized access control modifications. There is no direct confidentiality or availability impact reported. No known exploits are currently observed in the wild.

Summary

SuperTokens Core versions prior to 11.3.6, from 11.4.0 up to but not including 11.4.6, and from 12.0.6 up to but not including 12.0.8 contain an authentication bypass vulnerability (CWE-288). The vulnerability arises because app-specific management requests using an unknown tenant path combined with older CDI versions bypass API-key and public-tenant enforcement checks. Specifically, in the WebserverAPI.java source, the methods checkIPAccess and assertThatAPIKeyCheckPasses suppress TenantOrAppNotFoundException, while the app-specific handler resolves app/public storage and the public-tenant guard only applies to CDI versions 5.0 and later. This allows unauthenticated callers to access endpoints such as PUT /ghosttenant/recipe/role and GET /ghosttenant/recipe/roles to create and enumerate roles without valid API keys. The vulnerability is addressed in SuperTokens Core versions 11.3.6, 11.4.6, and 12.0.8.

CWE-288Authentication Bypass Using an Alternate Path or Channel (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product requires authentication, but the product has an alternate path or channel that does not require authentication.
Architecture and Design
Funnel all access through a single choke point to simplify how users can access a resource. For every access, perform a check to determine if the user has permissions to access the resource.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V1.2.3 (opens in a new tab)
V1.2.2 (opens in a new tab)
V1.2.4 (opens in a new tab)
Attack patterns
Directory Indexing (opens in a new tab)
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Nov 2026, 18:04 UTC

WeaknessesCWE-288

Technical details

References

Community reviews

Related threats