CVE-2026-44671 is a high-severity security vulnerability in github.com/zitadel/zitadel (go), affecting versions >= 4.0.0, <= 4.14.0. It is fixed in 4.15.0, 3.4.10.
Summary 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. Impact 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. Note that an authentication bypass is not possible. Affected Versions Systems integrating LDAP as IdPs and running one of the following versions are affected: 4.x: 4.0.0 through 4.14.0 (including RC versions) 3.x: 3.1.0 through 3.4.9 2.x: 2.71.11 through 2.71.19 Patches The vulnerability has been addressed in the latest releases. The patch resolves the issue by requiring the correct permission in case the verification flag is provided and only allows self-management of the email address, resp. phone number itself. 4.x: Upgrade to >=4.15.0 3.x: Update to >=3.4.10 2.x: Update to >=3.4.10 Workarounds The recommended solution is to upgrade to a patched version. If an immediate upgrade is not possible, developers should ensure their project's LDAP directory has strict access controls to limit the scope of information disclosure. Questions If there are any questions or comments about this advisory, please send an email to [email protected] Credits This vulnerability was identified and reported by ProScan AppSec (https://proscan.one/).
CVE-2026-44671 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (4.15.0, 3.4.10). Upgrading removes the vulnerable code path.
go
github.com/zitadel/zitadel (>= 4.0.0, <= 4.14.0)github.com/zitadel/zitadel (>= 2.71.11, <= 2.71.19)github.com/zitadel/zitadel (>= 3.1.0, <= 3.4.9)github.com/zitadel/zitadel → 4.15.0 (go)github.com/zitadel/zitadel → 3.4.10 (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-44671 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-44671 is reachable in your applications. Get a demo
Upgrade the following packages to resolve this vulnerability:
github.com/zitadel/zitadel to 4.15.0 or latergithub.com/zitadel/zitadel to 3.4.10 or laterKodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-44671 is a high-severity security vulnerability in github.com/zitadel/zitadel (go), affecting versions >= 4.0.0, <= 4.14.0. It is fixed in 4.15.0, 3.4.10.
CVE-2026-44671 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
github.com/zitadel/zitadel (go) versions >= 4.0.0, <= 4.14.0 is affected.
Yes. CVE-2026-44671 is fixed in 4.15.0, 3.4.10. Upgrade to this version or later.
Whether CVE-2026-44671 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
github.com/zitadel/zitadel to 4.15.0 or latergithub.com/zitadel/zitadel to 3.4.10 or later