Most recent entries from all

EUVD-2026-162922

fkie_cve-2023-47111

ZITADEL provides identity infrastructure. ZITADEL provides administrators the possibility to define a `Lockout Policy` with a maximum amount of failed password check attempts. On every failed password check, the amount of failed checks is compared against the configured maximum. Exceeding the limit, will lock the user and prevent further authentication. In the affected implementation it was possible for an attacker to start multiple parallel password checks, giving him the possibility to try out more combinations than configured in the `Lockout Policy`. This vulnerability has been patched in versions 2.40.5 and 2.38.3.

GHSA-7h8m-vrxx-vr4m — ZITADEL race condition in lockout policy execution

Affected: Go: github.com/zitadel/zitadel

### Impact

ZITADEL provides administrators the possibility to define a `Lockout Policy` with a maximum amount of failed password check attempts. On every failed password check, the amount of failed checks is compared against the configured maximum. Exceeding the limit, will lock the user and prevent further authentication.

In the affected implementation it was possible for an attacker to start multiple parallel password checks, giving him the possibility to try out more combinations than configured in the `Lockout Policy`.

### Patches

2.x versions are fixed on >= [2.40.5](https://github.com/zitadel/zitadel/releases/tag/v2.40.5) 2.38.x versions are fixed on >= [2.38.3](https://github.com/zitadel/zitadel/releases/tag/v2.38.3)

### Workarounds

There is no workaround since a patch is already available.

### References

None

### Questions

If you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com)

Most recent entries from all

EUVD-2026-162922

fkie_cve-2023-47111

GHSA-7h8m-vrxx-vr4m — ZITADEL race condition in lockout policy execution

gsd-2023-47111