CVE-2026-44671
highPriorität · verfolgen · 0EPSS 0.005 · 41. PerzentilEUUSEPSS · bewertet 2026-10-27
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.
cvss
Technischer Schweregrad, 0–10. Eine Zeile je Quelle.
Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen⚠ Quellen uneinig · medium–high · 6.9–7.5
SSVC
Eine Handlungsentscheidung — aus Ausnutzung und Auswirkung.
schwächen
Die CWE-Schwächeklassen, zu denen dies gehört.
betroffene Produkte (8)
Betroffene Produkte und Versionsbereiche.
Advisories (2)
Hersteller- und Ökosystem-Meldungen dazu.
- GHSA-rxvx-hhpj-q6pxZITADEL has LDAP Filter Injection in Login Flow2026-05-08ghsa · osvUS
## 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](https://github.com/zitadel/zitadel/releases/tag/v4.15.0) - **3.x**: Update to >=[3.4.10](https://github.com/zitadel/zitadel/releases/tag/v3.4.10) - **2.x**: Update to >=[3.4.10](https://github.com/zitadel/zitadel/releases/tag/v3.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 [security@zitadel.com](mailto:security@zitadel.com) ## Credits This vulnerability was identified and reported by **ProScan AppSec** ([https://proscan.one/](https://proscan.one)).
- GO-2026-5648ZITADEL has LDAP Filter Injection in Login Flow in github.com/zitadel/zitadel2026-06-25vendor · osvUS
ZITADEL has LDAP Filter Injection in Login Flow in github.com/zitadel/zitadel. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/zitadel/zitadel from v3.1.0 before v3.4.10; github.com/zitadel/zitadel from v4.0.0 before v4.15.0.
auch bekannt als (5)
Weitere Namen und Kennungen dieser Entität.
quellen
Welche Quellen diesen Datensatz belegen und wann.
Referenzen (8)
Externe Belege — Patches, Meldungen, Analysen.
- https://nvd.nist.gov/vuln/detail/CVE-2026-44671cnnvd
- https://zitadel.com/Patchcnnvd
- https://github.com/zitadel/zitadel/releases/tag/v3.4.10enisa_euvd
- https://github.com/zitadel/zitadel/releases/tag/v4.15.0enisa_euvd
- https://github.com/zitadel/zitadel/security/advisories/GHSA-rxvx-hhpj-q6pxenisa_euvd
- https://github.com/zitadel/zitadel/releases/tag/v3.4.10ProductRelease Notesnvd
- https://github.com/zitadel/zitadel/releases/tag/v4.15.0ProductRelease Notesnvd
- https://github.com/zitadel/zitadel/security/advisories/GHSA-rxvx-hhpj-q6pxMitigationPatchVendor Advisorynvd
Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan