ZITADEL has LDAP Filter Injection in Login Flow
Published 8 May 2026 · Updated 25 Jun 2026
Is your project on an affected github.com/zitadel/zitadel?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=4.0.0 <4.15.0
- Fixed in
- 4.15.0
go get github.com/zitadel/zitadel@v4.15.0- Affected
- >=2.71.11 <=2.71.19
- Fixed in
- No fix released
- Affected
- >=3.1.0 <3.4.10
- Fixed in
- 3.4.10
go get github.com/zitadel/zitadel@v3.4.10Details
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.0through4.14.0(including RC versions) - 3.x:
3.1.0through3.4.9 - 2.x:
2.71.11through2.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.
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 [security@zitadel.com](mailto:security@zitadel.com)
Credits
This vulnerability was identified and reported by ProScan AppSec (https://proscan.one/).
Is GHSA-rxvx-hhpj-q6px in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/zitadel/zitadel, and gives you the command that fixes it.
More advisories for github.com/zitadel/zitadel
- LowCVE-2026-85056ZITADEL: MFA bypass via session reuse in Login V2 in github.com/zitadel/zitadel · 1 Oct 2026
- LowCVE-2026-85057ZITADEL: Actions V1 sandbox escape: host file read via require() in github.com/zitadel/zitadel · 1 Oct 2026
- HighCVE-2026-85056ZITADEL: MFA bypass via session reuse in Login V2 · 24 Sept 2026
- HighCVE-2026-85057ZITADEL: Actions V1 sandbox escape: host file read via require() · 24 Sept 2026
- LowCVE-2026-56665ZITADEL: Missing Token Expiration (`exp`) Validation in JWT IdP Provider in github.com/zitadel/zitadel · 16 Sept 2026
- LowCVE-2026-56666ZITADEL: Auto-linking by email: IdP-side email verification is not checked in github.com/zitadel/zitadel · 16 Sept 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.