SSRF (Server-Side Request Forgery) in github.com/zitadel/zitadel (CVE-2026-55671)
Summary
SSRF in github.com/zitadel/zitadel (CVE-2026-55671). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2 or later.
Original description
The description as published by the source.
ZITADEL is an open source identity management platform. From 4.0.0-rc.1 through 4.15.1, ZITADEL's HTTP notification channels, OIDC BackChannel Logout, and SAML metadata URL fetches do not consistently validate user-defined URLs against protected denylist handling, allowing server-side requests to loopback, internal IP, link-local, or redirected endpoints through DNS rebinding, redirects, or protocol downgrades. 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-55671 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.20260615133614-8e82ec1cb9a2 or later.
If unsure, ask your IT team or search "github.com/zitadel/zitadel CVE-2026-55671" on the vendor's site.
CVE-2026-55671 (github.com/zitadel/zitadel) — CWE-918
Patched: 1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2 — 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.
SSRF (CWE-918) 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.20260615133614-8e82ec1cb9a2.
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.20260615133614-8e82ec1cb9a2ステージング環境で 1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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
- web github.com
- web github.com
- web github.com