Vulnerability in github.com/zitadel/zitadel (CVE-2026-44671)
Summary
Vulnerability in github.com/zitadel/zitadel (CVE-2026-44671). Confidential information can be exposed externally. Mitigation: upgrade to 3.4.10 or later.
Original description
The description as published by the source.
ZITADEL is an open source identity management platform. From 2.71.11 to before 3.4.10 and 4.15.0, a vulnerability was discovered in Zitadel's LDAP identity provider implementation, which fails to properly escape user-provided usernames before incorporating them into LDAP search filters. This allows unauthenticated attackers to perform LDAP Filter Injection during the login process. While this vulnerability does not allow for a full authentication bypass, an attacker can use LDAP metacharacters (such as *, (, )) to perform blind LDAP injection. By observing the different failure (or success) responses, an attacker can systematically enumerate valid usernames and extract sensitive attribute data from the connected LDAP directory. This vulnerability is fixed in 3.4.10 and 4.15.0.
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-44671 has been found in github.com/zitadel/zitadel.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade github.com/zitadel/zitadel to 3.4.10 or later.
If unsure, ask your IT team or search "github.com/zitadel/zitadel CVE-2026-44671" on the vendor's site.
CVE-2026-44671 (github.com/zitadel/zitadel) — CWE-90 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.4.10 — 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-90) exists in github.com/zitadel/zitadel.
Check the vendor advisory for the affected versions of github.com/zitadel/zitadel.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 3.4.10.
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 3.4.10ステージング環境で 3.4.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-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
- web github.com
- web github.com
- web github.com