# CVE-2026-44671: ZITADEL: LDAP Filter Injection in Login Flow

> Unauthenticated attackers can inject LDAP filters to enumerate usernames and extract sensitive directory data via blind injection.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-rxvx-hhpj-q6px, GO-2026-5648

## What is CVE-2026-44671?

CVE-2026-44671 is a high-severity vulnerability in zitadel, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-90 (Improper Neutralization of Special Elements used in an LDAP Query)

## Which versions are affected by CVE-2026-44671?

7 open source packages ship an affected version, including github.com/zitadel/zitadel. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/zitadel/zitadel` | Go | All versions | None |
| `github.com/zitadel/zitadel` | Go | From 2.71.11 to 2.71.19 | None |
| `github.com/zitadel/zitadel` | Go | From 2.71.11 to 2.71.19 | None |
| `github.com/zitadel/zitadel` | Go | From 3.1.0 | 3.4.10 |
| `github.com/zitadel/zitadel` | Go | From 3.1.0 | 3.4.10 |
| `github.com/zitadel/zitadel` | Go | From 4.0.0 | 4.15.0 |
| `github.com/zitadel/zitadel` | Go | From 4.0.0 | 4.15.0 |

Products: Zitadel Zitadel.

## How do I fix CVE-2026-44671?

Upgrade github.com/zitadel/zitadel to a fixed version for your release line: 3.4.10 or 4.15.0.

## Is CVE-2026-44671 being exploited?

There is no known exploitation of CVE-2026-44671 in the wild and no public exploit code.

## Other vulnerabilities in zitadel

- [CVE-2026-29191](https://insights.sbomify.com/CVE-2026-29191/): ZITADEL: 1-Click Account Takeover via XSS in /saml-post Endpoint (critical 9.3)
- [CVE-2025-67494](https://insights.sbomify.com/CVE-2025-67494/): ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login (critical 9.3)
- [CVE-2025-27507](https://insights.sbomify.com/CVE-2025-27507/): IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations (critical 9.0)
- [CVE-2025-64103](https://insights.sbomify.com/CVE-2025-64103/): Zitadel Bypass Second Authentication Factor (high 8.7)
- [CVE-2025-31123](https://insights.sbomify.com/CVE-2025-31123/): Zitadel Expired JWT Keys Usable for Authorization Grants (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44671 and fix it if it is affected.

What it is: CVE-2026-44671 is a high-severity vulnerability in zitadel, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44671 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/zitadel/zitadel (Go): affected all versions; no fix listed
- github.com/zitadel/zitadel (Go): affected from 2.71.11 up to 2.71.19; no fix listed
- github.com/zitadel/zitadel (Go): affected from 2.71.11 up to 2.71.19; no fix listed
- github.com/zitadel/zitadel (Go): affected from 3.1.0; fixed in 3.4.10
- github.com/zitadel/zitadel (Go): affected from 3.1.0; fixed in 3.4.10
- github.com/zitadel/zitadel (Go): affected from 4.0.0; fixed in 4.15.0
- github.com/zitadel/zitadel (Go): affected from 4.0.0; fixed in 4.15.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44671/ (Markdown: https://insights.sbomify.com/CVE-2026-44671/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44671
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44671
- OSV: https://osv.dev/vulnerability/CVE-2026-44671

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44671/
Summaries are generated and may contain mistakes; the official description above is the record.