supertokens-core: Improper Authentication
CVE-2026-123802 is a high-severity improper authentication vulnerability in supertokens-core from Supertokens, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected supertokens-core versions: >= 11.3.0, < 11.3.8; >= 11.4.0, < 11.4.8; >= 12.0.0, < 12.0.11, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.3% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of supertokens-core you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Supertokens | supertokens-core | >= 11.3.0, < 11.3.8; >= 11.4.0, < 11.4.8; >= 12.0.0, < 12.0.11; >= 12.1.0, < 12.1.2; >= 12.2.0, < 12.2.1; >= 12.3.0, < 12.3.1 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. Scored by CNA (github.com).
Official description
SuperTokens Core is an open source authentication server. From 11.3.0 until 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, and 12.3.1, a licensed deployment with a configured SAML client can authenticate an identity from an assertion that did not satisfy the audience check. When the identity provider uses assertion-level signing, an attacker who has a still-valid IdP-signed assertion naming the victim for any audience and the attacker's own valid assertion for the target audience can combine them because validateSamlResponseAudience accepts an audience from one assertion while extractAllClaims takes the final NameID and attributes from another; response-level signing does not expose this multi-assertion variant. Independently, an assertion from an identity provider configured for the target deployment but issued to another SuperTokens deployment using the shared default saml_sp_entity_id can satisfy the target's audience check. Successful exploitation authenticates the attacker as the victim IdP user. This issue is fixed in versions 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, and 12.3.1.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/supertokens/supertokens-core/commit/00a15e045323ba8a566ca6f59b70125b4030ab6c
- github.com/supertokens/supertokens-core/commit/1645915320c5dfc22bce9029eb7d8364f8df402f
- github.com/supertokens/supertokens-core/commit/1d0fd5b40848629295cf86d47be185f92f31e445
- github.com/supertokens/supertokens-core/commit/324686349b21ab46fe465ca5f74294d6c68d3859
- github.com/supertokens/supertokens-core/commit/53f42f496477e7cc3ccd48fe57851fa08d06a248
- github.com/supertokens/supertokens-core/commit/5ffdd887b470035f409d61f85f2186381ad9cdd6
- github.com/supertokens/supertokens-core/commit/8e69a85e38709b832869c3bfc83df9a150d6f3cf
- github.com/supertokens/supertokens-core/commit/a2483b692d43294fdb9ad2f8f6f831cca8300081
- github.com/supertokens/supertokens-core/commit/b21760ceb5089b0fa30c8fd46f7bbfc680de56dd
- github.com/supertokens/supertokens-core/commit/c77b13061176d9bd50ed24a9cf50ffbcdf332ee5
- github.com/supertokens/supertokens-core/commit/f4ddc022ef1ee17933efb710c21a960cb4ada083
- 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
Other vulnerabilities in supertokens-core
- 8.1 High severity
- 7.4 High severity
- 9.9 Critical severity
- 7.4 High severity
- 8.1 High severity
- 7.5 High severity
Recent Improper Authentication vulnerabilities
- 7.3 High severity
- 8.1 High severity
- 9.8 Critical severity
- 7.3 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.