Authentication Bypass in github.com/zitadel/zitadel (CVE-2026-55672)
Summary
Authentication bypass in github.com/zitadel/zitadel (CVE-2026-55672). Confidential information can be exposed externally. Exploitable via CodeExchange. Mitigation: upgrade to 1.80.0-v2.20.0.20260616131956-0973b074b488 or later.
Original description
The description as published by the source.
ZITADEL is an open source identity management platform. Prior to 3.4.12 and 4.15.2, ZITADEL's OAuth2 and OIDC CodeExchange, RefreshToken, and device token flows fail to verify that the requesting client matches the client that initiated the authorization flow, allowing intercepted grants or refresh tokens to be exchanged under a different client. This issue is fixed in versions 3.4.12 and 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-55672 has been found in github.com/zitadel/zitadel.
Attackers can target a specific entry point like CodeExchange over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20260616131956-0973b074b488 or later.
If unsure, ask your IT team or search "github.com/zitadel/zitadel CVE-2026-55672" on the vendor's site.
CVE-2026-55672 (github.com/zitadel/zitadel) — CWE-287 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: CodeExchange / RefreshToken / ClientB / code_verifier
Patched: 1.80.0-v2.20.0.20260616131956-0973b074b488 — apply immediately
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.
Authentication bypass (CWE-287) exists in github.com/zitadel/zitadel. Attackers reach the vulnerable code path via CodeExchange without authentication.
Check the vendor advisory for the affected versions of github.com/zitadel/zitadel. Attack surface: CodeExchange / RefreshToken / ClientB / code_verifier.
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.
Update to 1.80.0-v2.20.0.20260616131956-0973b074b488.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20260616131956-0973b074b488ステージング環境で 1.80.0-v2.20.0.20260616131956-0973b074b488 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com
- web github.com