ChainzitadelGo:github.com/zitadel/zitadel/v2
zitadel: successive fixes (2025–2026)
3 CVEs over 3 generations, 30 May 2025 to 7 Mar 2026.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2025-4893630 May 2025 First in the chain
- CVE-2025-6410129 Oct 2025 next fix after CVE-2025-48936
- CVE-2026-290677 Mar 2026 next fix after CVE-2025-64101
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2025-48936 | 30 May 2025 | ZITADEL Allows Account Takeover via Malicious X-Forwarded-Proto Header Injection · fixed in 3.2.2 | First in chain | 12.7 |
| CVE-2025-64101 | 29 Oct 2025 | ZITADEL Vulnerable to Account Takeover via Malicious Forwarded Header Injection · fixed in 2.71.18 | CVE-2025-48936 · Next fix in the same package · Medium | 11.7 |
| CVE-2026-29067 | 7 Mar 2026 | ZITADEL: Account Takeover Due to Improper Instance Validation in V2 Login · fixed in 1.80.0-v2.20.0.20251208091519-4c879b47334e | CVE-2025-64101 · Next fix in the same package · Medium | 11.2 |