ZITADEL race condition in lockout policy execution

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

EPSS

• CVE-2023-47111: 0.52% estimated exploitation activity in the next 30 days; percentile 43.99 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 2.38.x versions are fixed on = 2.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

Published by the source

8 Nov 2023, 17:52 UTC

Last modified by the source

9 Nov 2023, 16:14 UTC

Source last checked

26 Oct 2026, 15:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7h8m-vrxx-vr4m

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

# Patch Next advisory brief: CVE-2023-47111

Advisory: ZITADEL race condition in lockout policy execution
IDs: CVE-2023-47111, GHSA-7h8m-vrxx-vr4m
Record: https://patchnext.com/advisories/cve-2023-47111 (revision 1, source checked 26 Oct 2026, 15:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
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.40.5, 2.38.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zitadel/zitadel: affected >= 2.39.0, < 2.40.5; < 2.38.3; fixed in 2.38.3, 2.40.5

## 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-7h8m-vrxx-vr4m (GitHub-reviewed advisory GHSA-7h8m-vrxx-vr4m lists affected ranges: Go github.com/zitadel/zitadel >=2.39.0 =0 <2.38.3)

Commands are suggestions: review each one before running it.