All reports
Medium

ZITADEL "ignoring unknown usernames" vulnerability

Affected versions

Version ranges need review.

Affected versions
>= 2.55.0, <= 2.55.4
Fixed version
2.55.5
Affected versions
>= 2.54.0, <= 2.54.7
Fixed version
2.54.8
Affected versions
*
Fixed version
Not reported
Affected versions
>= 2.53.0, <= 2.53.8
Fixed version
2.53.9
Affected versions
>= 0.0.0-20230609131415-dafa8ab4dfe8, < 0.0.0-20240731122357-a1d24353db4d
Fixed version
0.0.0-20240731122357-a1d24353db4d
Affected versions
= 2.58.0
Fixed version
2.58.1
Affected versions
>= 2.56.0, <= 2.56.1
Fixed version
2.56.2
Affected versions
>= 1.80.0-v2.20.0.20230609131415-dafa8ab4dfe8, < 1.80.0-v2.20.0.20240731122357-a1d24353db4d
Fixed version
1.80.0-v2.20.0.20240731122357-a1d24353db4d
Affected versions
= 2.57.0
Fixed version
2.57.1

Exploitation

CVE-2024-41952

Probability of exploitation in the next 30 days: 0.63%

FIRST EPSS · 2026-11-21

Description

Impact

ZITADEL administrators can enable a setting called "Ignoring unknown usernames" which helps mitigate attacks that try to guess/enumerate usernames. If enabled, ZITADEL will show the password prompt even if the user doesn't exist and report "Username or Password invalid". Due to a implementation change to prevent deadlocks calling the database, the flag would not be correctly respected in all cases and an attacker would gain information if an account exist within ZITADEL, since the error message shows "object not found" instead of the generic error message.

Patches

2.x versions are fixed on >= 2.58.1 2.57.x versions are fixed on >= 2.57.1 2.56.x versions are fixed on >= 2.56.2 2.55.x versions are fixed on >= 2.55.5 2.54.x versions are fixed on >= 2.54.8 2.53.x versions are fixed on >= 2.53.9

ZITADEL recommends upgrading to the latest versions available in due course.

Workarounds

There is no workaround since a patch is already available.

Questions

If you have any questions or comments about this advisory, please email us at security@zitadel.com

Links

Credits

  • livio-a