SUPERTOKENS CORE · CVE-2026-123798 · Runtime
NO FIX YET · SEE WHAT TO DO
SuperTokens Core accepts a validly signed SAML response without confirming that the signed element is the one used for login. A user of the configured identity provider can wrap a signed element and supply their own identity, which authenticates them as another user.
first public Oct 16, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Any application that uses SuperTokens Core with SAML single sign-on is exposed, and the risk comes from anyone with an account at the configured identity provider. Both response-level and assertion-level signing are affected, and SP-initiated login is reachable without enabling allowIDPInitiatedLogin. Teams that do not use SAML, or that run a fixed version, can skip it.
Not affected if patched-version, saml-not-used
Who cares saml, self-hosted, supertokens-core
Unknown from the sources.
11.3.7, 11.4.7, or 12.0.10, matching your release line.SuperTokens Core is an open source authentication server. From 11.3.0 until 11.3.7, 11.4.7, and 12.0.10, SAML.verifySamlResponseSignature calls OpenSAML SignatureValidator.validate without first applying SAMLSignatureProfileValidator. The Core can therefore accept a cryptographically valid signature that references a different XML element from the Response or Assertion whose NameID and attributes are used for authentication. An ordinary user of the configured identity provider can move a genuinely signed element elsewhere in the document while supplying an attacker-authored identity-bearing element, causing XML Signature Wrapping authentication as another IdP user. Both response-level and assertion-level signing paths are affected, and SP-initiated login remains reachable without enabling allowIDPInitiatedLogin. This issue is fixed in versions 11.3.7, 11.4.7, and 12.0.10.
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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.