SuperTokens Core SAML lets attackers sign in as other IdP users
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-287.
Summary
SuperTokens Core releases from 11.3.0 before 11.3.8, from 11.4.0 before 11.4.8, from 12.0.0 before 12.0.11, from 12.1.0 before 12.1.2, from 12.2.0 before 12.2.1 and from 12.3.0 before 12.3.1 are affected. With assertion-level signing, the SAML audience check and the identity extraction can use different assertions, so an attacker who holds a valid IdP-signed assertion for a victim can combine it with their own assertion and sign in as that victim (CWE-287).
Written with Claude Haiku 5.5 from the sources below · 2026-11-09
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| supertokens | supertokens-core | 11.3.0 to before 11.3.8; 11.4.0 to before 11.4.8; 12.0.0 to before 12.0.11; 12.1.0 to before 12.1.2; 12.2.0 to before 12.2.1; 12.3.0 to before 12.3.1 | 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, 12.3.1 | Patch available | CNA |
- supertokens-core Vendorsupertokens Affected 11.3.0 to before 11.3.8; 11.4.0 to before 11.4.8; 12.0.0 to before 12.0.11; 12.1.0 to before 12.1.2; 12.2.0 to before 12.2.1; 12.3.0 to before 12.3.1 Fixed in 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, 12.3.1 Patch available CNA
Remediation
Upgrade SuperTokens Core to 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1 or 12.3.1, matching the release line you run.
Written with Claude Haiku 5.5 from the sources below · 2026-11-09
- Fix · CNA supertokens-core (supertokens) Fixed in 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, 12.3.1
Timeline
- 2026-11-09 Threatist record created from CVE-2026-123802
- 2026-11-11 Priority changed: MEDIUM → LOW
- 2026-11-13 CISA SSVC decision points changed
References
Other 18
- https://github.com/supertokens/supertokens-core/security/advisories/GHSA-wfg2-vqfg-rqh6
- https://github.com/supertokens/supertokens-core/commit/00a15e045323ba8a566ca6f59b70125b4030ab6c
- https://github.com/supertokens/supertokens-core/commit/1645915320c5dfc22bce9029eb7d8364f8df402f
- https://github.com/supertokens/supertokens-core/commit/1d0fd5b40848629295cf86d47be185f92f31e445
- https://github.com/supertokens/supertokens-core/commit/324686349b21ab46fe465ca5f74294d6c68d3859
- https://github.com/supertokens/supertokens-core/commit/53f42f496477e7cc3ccd48fe57851fa08d06a248
- https://github.com/supertokens/supertokens-core/commit/5ffdd887b470035f409d61f85f2186381ad9cdd6
- https://github.com/supertokens/supertokens-core/commit/8e69a85e38709b832869c3bfc83df9a150d6f3cf
- https://github.com/supertokens/supertokens-core/commit/a2483b692d43294fdb9ad2f8f6f831cca8300081
- https://github.com/supertokens/supertokens-core/commit/b21760ceb5089b0fa30c8fd46f7bbfc680de56dd
- https://github.com/supertokens/supertokens-core/commit/c77b13061176d9bd50ed24a9cf50ffbcdf332ee5
- https://github.com/supertokens/supertokens-core/commit/f4ddc022ef1ee17933efb710c21a960cb4ada083
- https://github.com/supertokens/supertokens-core/releases/tag/v11.3.8
- https://github.com/supertokens/supertokens-core/releases/tag/v11.4.8
- https://github.com/supertokens/supertokens-core/releases/tag/v12.0.11
- https://github.com/supertokens/supertokens-core/releases/tag/v12.1.2
- https://github.com/supertokens/supertokens-core/releases/tag/v12.2.1
- https://github.com/supertokens/supertokens-core/releases/tag/v12.3.1
More supertokens vulnerabilities
- TI-2026-28002 A lack of tenant separation in SuperTokens Inc. CVSS 3.1CRITICAL 9.6
- TI-2026-87196 SuperTokens Core app API key can overwrite parent domain credentials CVSS 3.1CRITICAL 9.9
- TI-2026-87188 Unknown tenant path bypasses API key enforcement in SuperTokens Core CVSS 3.1HIGH 7.5
- TI-2026-87206 WebAuthn sign-in in SuperTokens Core accepts passkeys across tenants CVSS 3.1HIGH 8.1
- TI-2026-87194 SAML signature wrapping in SuperTokens Core lets users log in as others CVSS 3.1HIGH 8.1
- TI-2026-87195 SuperTokens Core accepts expired dashboard sessions CVSS 3.1HIGH 7.4
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences