Vulnerability in github.com/zitadel/zitadel (CVE-2026-55670)
Summary
Vulnerability in github.com/zitadel/zitadel (CVE-2026-55670). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.80.0-v2.20.0.20260615092437-6082e59d47c1 or later.
Original description
The description as published by the source.
ZITADEL is an open source identity management platform. Prior to 4.15.1, ZITADEL's event store validation can retain the original resource owner for a deleted user identifier, causing a later user recreated with the same identifier in another organization to be provisioned under the original organization and exposed to that organization's administrator. This issue is fixed in version 4.15.2.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55670 has been found in github.com/zitadel/zitadel.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20260615092437-6082e59d47c1 or later.
If unsure, ask your IT team or search "github.com/zitadel/zitadel CVE-2026-55670" on the vendor's site.
CVE-2026-55670 (github.com/zitadel/zitadel) — CWE-284
Patched: 1.80.0-v2.20.0.20260615092437-6082e59d47c1 — apply immediately
Workaround: The recommended solution is to upgrade to a patched version.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-284) exists in github.com/zitadel/zitadel.
Check the vendor advisory for the affected versions of github.com/zitadel/zitadel.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.80.0-v2.20.0.20260615092437-6082e59d47c1.
Workaround: The recommended solution is to upgrade to a patched version.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/zitadel/zitadel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/zitadel/zitadel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/zitadel/zitadelを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
The recommended solution is to upgrade to a patched version.パッチが適用されるまでの応急処置として、The recommended solution is to upgrade to a patched version. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20260615092437-6082e59d47c1ステージング環境で 1.80.0-v2.20.0.20260615092437-6082e59d47c1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com