Read the docs

SAML signature wrapping in SuperTokens Core lets users log in as others

Priority LOW 37CWE-287Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-287.

Summary

SuperTokens Core (supertokens-core) from 11.3.0 before 11.3.7, from 11.4.0 before 11.4.7, and from 12.0.6 before 12.0.10 checks SAML signatures without first applying the signature profile validation. A valid signature can then cover a different XML element than the one whose NameID is used, enabling XML Signature Wrapping (CWE-347). An ordinary user of the configured identity provider can authenticate as another IdP user.

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.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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00209 11th percentileScored 2026-11-16
Fix Fixed supertokens-core (supertokens): 12.0.10, 11.4.7, 11.3.7

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

VendorProductAffected versionsFixed inStatusSource
supertokenssupertokens-core12.0.6 to before 12.0.10; 11.4.0 to before 11.4.7; 11.3.0 to before 11.3.712.0.10, 11.4.7, 11.3.7Patch availableCNA
  • supertokens-core Vendorsupertokens Affected 12.0.6 to before 12.0.10; 11.4.0 to before 11.4.7; 11.3.0 to before 11.3.7 Fixed in 12.0.10, 11.4.7, 11.3.7 Patch available CNA

Remediation

Upgrade supertokens-core to 11.3.7, 11.4.7, or 12.0.10, matching the release line you run.

Written with Claude Haiku 5.5 from the sources below · 2026-11-09

  • Fix · CNA supertokens-core (supertokens) Fixed in 12.0.10, 11.4.7, 11.3.7

Timeline

  1. 2026-11-09 Threatist record created from CVE-2026-123798
  2. 2026-11-11 Priority changed: MEDIUM → LOW
  3. 2026-11-13 CISA SSVC decision points changed

References

  • 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-87195 SuperTokens Core accepts expired dashboard sessions CVSS 3.1HIGH 7.4
See all 8 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences