GHSA-gvx2-mwmj-wwvj: SuperTokens Core: SAML XML Signature Wrapping authentication bypass — any IdP user can authenticate as any other user

Published Nov 9, 2026
·
Updated

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.

Affected Software

1 affected component
SuperTokens SuperTokens Core>=11.3.0<11.3.7, >=11.4.0<11.4.7, >=12.0.0<12.0.10

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade SuperTokens Core to a version that resolves this vulnerability.

    Fixed in 11.3.7
  2. Upgrade

    Upgrade SuperTokens Core to a version that resolves this vulnerability.

    Fixed in 11.4.7
  3. Upgrade

    Upgrade SuperTokens Core to a version that resolves this vulnerability.

    Fixed in 12.0.10

Event History

Nov 9, 2026
CVE Published
via OSV·06:04 PM
Data Sourced
via OSV·06:04 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

SuperTokens Core deployments running versions from 11.3.0 up to, but not including, 11.3.7, 11.4.7, or 12.0.10 are affected when using SAML authentication. Both response-level and assertion-level SAML signing paths are affected.

2

What does an attacker need to exploit this issue?

The attacker needs to be an ordinary user of the configured identity provider and obtain a genuinely signed SAML element. They can then alter the XML document so that an attacker-controlled Response or Assertion supplies the NameID and attributes used for authentication.

3

Is IdP-initiated login required for exploitation?

No. SP-initiated login remains reachable even when allowIDPInitiatedLogin is not enabled.

4

How should affected deployments be remediated?

Upgrade SuperTokens Core to 11.3.7, 11.4.7, or 12.0.10, as appropriate for the deployed release line.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203