SAML callback in SuperTokens Core accepts replayed login responses
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass, Spoofing
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-294 and CWE-384.
Summary
SuperTokens Core 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 does not consume RelayState or enforce InResponseTo in its SAML callback (CWE-294). An attacker who captures a valid SAML response and its RelayState can replay them to the callback before the assertion expires, minting a new authorization code for the captured identity.
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, SAML.handleCallback does not consume RelayState, record assertion identifiers, or enforce Response.InResponseTo. In the SP-initiated flow, an attacker who obtains a legitimately issued, still-valid SAML response and its matching RelayState can resubmit the pair to /recipe/saml/callback before the assertion's NotOnOrAfter time; in the IdP-initiated flow, the assertion can be replayed without RelayState. The missing Response.InResponseTo check also permits an in-progress login to be completed with an assertion for a different identity and fails to enforce allowIDPInitiatedLogin=false. The callback does not validate Destination or SubjectConfirmationData Recipient and NotOnOrAfter, and each accepted callback mints a fresh, independently redeemable authorization code carrying the captured user's identity. 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 version 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1 or 12.3.1, whichever is the fixed release on your current branch.
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-123801
- 2026-11-10 CISA SSVC decision points changed
- 2026-11-10 Priority changed: MEDIUM → LOW
References
Other 13
- https://github.com/supertokens/supertokens-core/security/advisories/GHSA-3r7x-rhvc-fw28
- https://github.com/supertokens/supertokens-core/commit/075655222f5e72f3683a127e45c83c4174fbd4f7
- https://github.com/supertokens/supertokens-core/commit/4e05d8cf60287e9d2720140031a8b8f4430d056f
- https://github.com/supertokens/supertokens-core/commit/557835406547d269f5d0e33159630a1873461c38
- https://github.com/supertokens/supertokens-core/commit/5c42f02e98f67174c6a5a800dd9f8bd5b6e98486
- https://github.com/supertokens/supertokens-core/commit/b6730e608b2d4562939cd4f41ea07df5f841dfe5
- https://github.com/supertokens/supertokens-core/commit/ca2bca9bc900c2fd399d508818ad026cc977dcf6
- 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-87198 SuperTokens Core SAML lets attackers sign in as other IdP users 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
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences