SuperTokens Core: Unknown tenant path bypasses API key and public-tenant enforcement
Affects supertokens-core below 11.3.6, 11.4.0 to 11.4.5, and 12.0.6 to 12.0.7 when API_KEYS is set and UserRoles is enabled. Fixed in 11.3.6, 11.4.6, and 12.0.8.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 11.3.6, 11.4.6, 12.0.8
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 11.3.6, 11.4.6, 12.0.8.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
SuperTokens Core is an open source authentication server. Prior to 11.3.6, 11.4.6, and 12.0.8, app-specific management requests using an unknown tenant path and an older supported cdi-version can bypass API-key and public-tenant enforcement. In src/main/java/io/supertokens/webserver/WebserverAPI.java, checkIPAccess and assertThatAPIKeyCheckPasses suppress TenantOrAppNotFoundException, while the later app-specific handler resolves app/public storage and the public-tenant guard applies only to CDI versions 5.0 and later. An unauthenticated caller able to reach the Core endpoint can therefore use PUT /ghosttenant/recipe/role and GET /ghosttenant/recipe/roles to create and enumerate application roles without a valid API key. This issue is fixed in versions 11.3.6, 11.4.6, and 12.0.8.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- 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
What to do
Upgrade to a fixed version: 11.3.6, 11.4.6, 12.0.8.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- supertokens supertokens-core
fixed in 11.3.6; From 11.4.0 · fixed in 11.4.6; From 12.0.6 · fixed in 12.0.8
Evidence 7
- Advisory
- Repository
- Repository
- Repository
- Repository
Show all 7 sourcesShow fewer sources
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123797
Is CVE-2026-123797 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
What does this mean?
A request with an unknown tenant path segment and an older but still supported cdi-version header, such as 3.0, can get past the API key check and public-tenant enforcement on the management API.Source: github.com
Which versions are affected by CVE-2026-123797?
supertokens-core: before 11.3.6; from 11.4.0 before 11.4.6; from 12.0.6 before 12.0.8.Source: cve.now feed data
Am I affected, and how do I check?
The advisory lists supertokens-core below 11.3.6, 11.4.0 through 11.4.5, and 12.0.6 through 12.0.7. To check a deployment, look at the installed core version and whether API_KEYS is configured for management API protection and the UserRoles recipe is enabled.Source: github.com
How do I fix CVE-2026-123797?
Upgrade to the fixed release on your version line: 11.3.6 for 11.3.x, 11.4.6 for 11.4.x, or 12.0.8 for 12.0.x.Source: github.com