SuperTokens Core up to 12.3.0 SAML Audience Validation validateSamlResponseAudience assertion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.70+ |
Summary
A vulnerability was found in SuperTokens Core up to 12.3.0 and classified as critical. The impacted element is the function validateSamlResponseAudience of the component SAML Audience Validation. Such manipulation leads to assertion.
This vulnerability is referenced as CVE-2026-123802. It is possible to launch the attack remotely. No exploit is available.
It is suggested to upgrade the affected component.
Details
A vulnerability was found in SuperTokens Core up to 12.3.0 and classified as critical. Affected by this issue is the function validateSamlResponseAudience of the component SAML Audience Validation. The manipulation with an unknown input leads to a assertion vulnerability. Using CWE to declare the problem leads to CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-123802 since 11/06/2026. The exploitation is known to be easy. The attack may be launched remotely. There are known technical details, but no exploit is available.
Upgrading to version 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1 or 12.3.1 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 11.3.0
- 11.3.1
- 11.3.2
- 11.3.3
- 11.3.4
- 11.3.5
- 11.3.6
- 11.3.7
- 11.4.0
- 11.4.1
- 11.4.2
- 11.4.3
- 11.4.4
- 11.4.5
- 11.4.6
- 11.4.7
- 12.0
- 12.0.0
- 12.0.1
- 12.0.2
- 12.0.3
- 12.0.4
- 12.0.5
- 12.0.6
- 12.0.7
- 12.0.8
- 12.0.9
- 12.0.10
- 12.1
- 12.1.0
- 12.1.1
- 12.2
- 12.2.0
- 12.3.0
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.1
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AssertionCWE: CWE-617
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Core 11.3.8/11.4.8/12.0.11/12.1.2/12.2.1/12.3.1
Timeline
11/06/2026 CVE reserved11/09/2026 Advisory disclosed
11/09/2026 VulDB entry created
11/09/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CNA: GitHub_M
CVE: CVE-2026-123802 (🔒)
GCVE (CVE): GCVE-0-2026-123802
GCVE (VulDB): GCVE-100-433220
Entry
Created: 11/09/2026 19:48Changes: 11/09/2026 19:48 (65)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.