CVE-2026-123802 · Runtime
NO FIX YET · SEE WHAT TO DO
SuperTokens Core is an open source authentication server whose SAML login path can accept an assertion that failed the audience check, by mixing claims from two signed assertions or reusing an IdP assertion issued to another deployment with the default saml_sp_entity_id. A successful attack authenticates the attacker as the victim's identity provider user.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Only deployments that run SuperTokens Core with a licensed SAML client configured are exposed. The default shared saml_sp_entity_id makes the second variant possible, and assertion-level signing by the identity provider makes the first. Deployments without SAML, or on the fixed versions, can skip it.
Not affected if custom-saml-sp-entity-id, fixed-version, no-saml-client
Who cares authentication, saml, self-hosted, supertokens
11.3.0 to 11.3.8, 11.4.x before 11.4.8, 12.0.x before 12.0.11, 12.1.x before 12.1.2, 12.2.x before 12.2.1, 12.3.x before ).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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
12.3.1saml_sp_entity_id is left at the shared default.11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, or 12.3.1 for the matching release line.NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.