Advisory record · GHSA-pr34-2v5x-6qjq

ZITADEL has 1-Click Account Takeover via XSS in /saml-post Endpoint

CVSS 9.3 CriticalCriticalEPSS 0.0046 · 40th percentile

Critical, because:

  • CVSS score 9.3: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 4 Mar 2026, 22:47 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/zitadel/zitadelGo>=4.0.0, <4.12.04.12.0
github.com/zitadel/zitadel/v2Go>=4.0.0, <4.12.04.12.0
Identifiers
GHSA-pr34-2v5x-6qjq · CVE-2026-29191 · GO-2026-4607
Weakness (CWE)
CWE-79
Published
4 Mar 2026
Updated
23 Mar 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

ZITADEL versions 4.0.0 through 4.11.1 (github.com/zitadel/zitadel and github.com/zitadel/zitadel/v2) are vulnerable to cross-site scripting through the /saml-post endpoint of the login V2 interface. An unauthenticated remote attacker can run JavaScript in users' browsers and reset their passwords to take over accounts, though accounts with MFA or passwordless authentication are mitigated. Upgrade to version 4.12.0 or later. If upgrading is not possible and SAML IdP integration is not needed, block access to the /saml-post endpoint with a WAF or reverse proxy rule.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.3 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0046, the 40th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:09 UTC First seen by agentprime
  2. 31 Oct 2026, 15:09 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.