dbcve.org
ZitadelApplication

CVE-2026-32132

HIGH · 7.4 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 3.4.8 / 4.12.2 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
ZITADEL is an open source identity management platform. Prior to 3.4.8 and 4.12.2, a potential vulnerability exists in Zitadel's passkey registration endpoints. This endpoint allows registering a new passkey using a previously retrieved code. An improper expiration check of the code, could allow an attacker to potentially register their own passkey and gain access to the victim's account. This vulnerability is fixed in 3.4.8 and 4.12.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

ZITADEL's passkey registration endpoint fails to properly validate code expiration before allowing passkey registration. An attacker who obtains a previously issued but expired registration code can register their own passkey to a victim's account, bypassing the intended time-limited registration flow.

MitigationUpgrade ZITADEL to version 3.4.8 or 4.12.2 or later to remediate the improper expiration check vulnerability in the passkey registration endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ZitadelApplication
Affected:< 3.4.8>= 4.0.0, < 4.12.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed ZITADEL version
    Run 'zitadel version' or check the version from the container image tag or binary used in your deployment
    Affected if Version is < 3.4.8 OR (version >= 4.0.0 AND version < 4.12.2)
  2. Verify passkey registration is enabled
    Check your ZITADEL configuration for passkey/WebAuthn settings, typically in the authentication policy or login settings via the console or API
    Affected if Passkey registration is available and users can enroll authentication methods through the registration flow
  3. Confirm registration code expiration settings
    Review the system settings or custom authentication flow configuration for passkey enrollment to see if time-limited codes are issued
    Affected if Your deployment uses time-limited registration codes for passkey enrollment that could become expired yet still be accepted

You are affected if your ZITADEL version falls within the vulnerable ranges AND your deployment uses passkey registration with time-limited codes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.4.8 / 4.12.2 or later
Fixed in 3.4.84.12.2
Interim mitigation

Upgrade ZITADEL to version 3.4.8 or 4.12.2 or later to remediate the improper expiration check vulnerability in the passkey registration endpoint.

Recommended fix High confidence

Upgrade to Zitadel 3.4.8 (for v3.x) or 4.12.2 (for v4.x)

  1. 1. Identify the current Zitadel version running in your environment
  2. 2. For Zitadel versions < 3.4.8: Plan upgrade to version 3.4.8
  3. 3. For Zitadel versions >= 4.0.0 and < 4.12.2: Plan upgrade to version 4.12.2
  4. 4. Review the Zitadel release notes for the target version to understand any changes or migration requirements
  5. 5. Back up your current Zitadel database and configuration
  6. 6. Perform the upgrade following Zitadel's standard upgrade procedure (typically: stop service, replace binary/container, run any pending migrations, restart service)
  7. 7. Verify the upgrade was successful by checking the Zitadel admin console or API
  8. 8. Test passkey registration functionality to confirm the vulnerability is resolved
Caveat Review release notes for version-specific breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zitadel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32132 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32132 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data