Servers and applications
GHSA-x4c7-fpcx-w9q6
SAML Identity-Provider Confusion in ZITADEL Leads to Account Takeover
- Severity
- High 8.7
- Published
- 28 Sept 2026
- Last changed
- 28 Sept 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 4.19.2
- Attack
- Over the network · Needs an administrator account · No user action needed
- Attacker can
- Read data · Change data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N- Sources
- Project advisories (GitHub)
Description
ZITADEL’s SAML identity-provider intent callback (the endpoint used by Login V2 and custom login UIs to complete an external SAML login) accepted an assertion signed by one configured SAML identity provider as proof of identity for a login started against a different SAML identity provider.
On an instance with two or more SAML identity providers, an attacker who can configure one SAML identity provider and controls its signing key could complete a login intent aimed at a second SAML identity provider and obtain an authenticated session as any user linked to that second provider, without any interaction from the victim. The callback selected the identity provider whose certificate verifies the assertion’s signature from the request URL, but resolved the local user account from the login intent, and never checked that the two identity providers were the same.
An attacker who can configure a SAML identity provider on the instance and controls that provider’s signing key can:
Workarounds
The recommended solution is to upgrade to a patched version. There is no configuration that fully closes this gap on unpatched versions.
As a partial mitigation, self-hosted deployments can disable public organization registration (DisallowPublicOrgRegistration) to remove the unauthenticated path to organization-administrator permission. This does not close the issue for existing organization administrators.
Affected software
| Software | Affected versions |
|---|---|
ZITADELServers and applications · github:zitadel/zitadel |
|
About ZITADEL
ZITADEL - Identity infrastructure, simplified for you.
- GitHub stars
- 15,585GitHub, 15 Nov 2026
- Forks
- 1,432GitHub, 15 Nov 2026
- Latest release
- v4.20.3GitHub, 15 Nov 2026
- Released
- 13 Nov 2026GitHub
- License
- AGPL-3.0GitHub
- First published on GitHub
- 16 Mar 2020GitHub
Vulnerabilities in ZITADEL
- In our list
- 103
- Published in the last 12 months
- 72
- Critical, last 12 months
- 13
- High, last 12 months
- 37
- Known exploited
- 0
- GHSA-qqv8-37gw-ww2qMissing second-factor check on authenticator enrollment in Login V2 (MFA bypass)High 8.1 18 Nov 2026
- GHSA-vg5j-vf6h-586mLogin V2 exposes internal functions as unauthenticated endpointsHigh 7.4 13 Nov 2026
- GHSA-3gwf-ph53-v73cLogin V2: authentication bypass via unauthenticated (zero-factor) session for OIDC and SAML requestsHigh 7.4 13 Nov 2026
- GHSA-gx82-3gqq-j4h5Session API and Login V2: organization login policy not enforced for password sign-inHigh 7.1 13 Nov 2026
- GHSA-fphg-99ff-7qrpLogin V2: external IdP sign-in callback not bound to the initiating browser (login CSRF / session swapping)Medium 5.4 13 Nov 2026
- GHSA-pm3x-9hh8-g745Login V2: Arbitrary Redirect URL AcceptedMedium 4.3 13 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-x4c7-fpcx-w9q6
- github.com https://github.com/zitadel/zitadel/security/advisories/GHSA-x4c7-fpcx-w9q6