CVE-2026-123801
SuperTokens Core: SAML callback accepts a replayed RelayState + SAMLResponse, minting a fresh authorization code on each replay
- High 7.4
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, 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.
Key facts
- Published
- 9 Nov 2026
- Last changed
- 10 Nov 2026
- Assigned by
- GitHub_M
- EPSS
- 0.353% likely to be exploited in the next 30 days, higher than 29.471% of CVEs (scores for 15 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: total
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 7.4CVSS 3.1, Highfrom the CNA (GitHub_M)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| supertokens | supertokens-core |
|
Timeline
- 9 Nov 2026 Published
Weakness
References
- 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