Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9

ZITADEL "ignoring unknown usernames" vulnerability

CVE-2024-41952GHSA-567v-6hmg-6qg7

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/zitadel/zitadel 2.58.1, 2.57.1, 2.56.2, 2.55.5, 2.54.8, 2.53.9, 1.80.0-v2.20.0.20240731122357-a1d24353db4d, 0.0.0-20240731122357-a1d24353db4d), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/zitadel/zitadel

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

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-567v-6hmg-6qg7 lists affected ranges: Go github.com/zitadel/zitadel >=2.53.0 =2.54.0 =2.55.0 =2.56.0 =2.57.0 =2.58.0 =0.0.0-20230609131415-dafa8ab4dfe8 =1.80.0-v2.20.0.20230609131415-dafa8ab4dfe8 <1.80.0-v2.20.0.20240731122357-a1d24353db4d

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2024-41952: 0.63% estimated exploitation activity in the next 30 days; percentile 50.39 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-567v-6hmg-6qg7

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-41952

Advisory: ZITADEL "ignoring unknown usernames" vulnerability
IDs: CVE-2024-41952, GHSA-567v-6hmg-6qg7
Record: https://patchnext.com/advisories/cve-2024-41952 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/zitadel/zitadel 2.58.1, 2.57.1, 2.56.2, 2.55.5, 2.54.8, 2.53.9, 1.80.0-v2.20.0.20240731122357-a1d24353db4d, 0.0.0-20240731122357-a1d24353db4d. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zitadel/zitadel: affected >= 2.53.0, <= 2.53.8; >= 2.54.0, <= 2.54.7; >= 2.55.0, <= 2.55.4; >= 2.56.0, <= 2.56.1; >= 2.57.0, <= 2.57.0; >= 2.58.0, <= 2.58.0; >= 0.0.0-20230609131415-dafa8ab4dfe8, < 0.0.0-20240731122357-a1d24353db4d; >= 1.80.0-v2.20.0.20230609131415-dafa8ab4dfe8, < 1.80.0-v2.20.0.20240731122357-a1d24353db4d; fixed in 0.0.0-20240731122357-a1d24353db4d, 2.55.5, 2.56.2, 2.57.1, 1.80.0-v2.20.0.20240731122357-a1d24353db4d, 2.54.8, 2.58.1, 2.53.9

## Suggested inspection (read-only)
- Go github.com/zitadel/zitadel: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/zitadel/zitadel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-567v-6hmg-6qg7 (GitHub-reviewed advisory GHSA-567v-6hmg-6qg7 lists affected ranges: Go github.com/zitadel/zitadel >=2.53.0 =2.54.0 =2.55.0 =2.56.0 =2.57.0 =2.58.0 =0.0.0-20230609131415-dafa8ab4dfe8 =1.80.0-v2.20.0.20230609131415-dafa8ab4dfe8 <1.80.0-v2.20.0.20240731122357-a1d24353db4d)

Commands are suggestions: review each one before running it.

Loading voting…