CVE-2026-32132
Improper Expiration Check in ZITADEL Passkey Registration Enables Account Takeover
Publication date: 2026-03-11
Last updated on: 2026-03-16
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| zitadel | zitadel | to 3.4.8 (exc) |
| zitadel | zitadel | From 4.0.0 (inc) to 4.12.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-613 | According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in ZITADEL's passkey registration endpoints prior to versions 3.4.8 and 4.12.2. The issue is due to an improper expiration check of a previously retrieved code used during passkey registration. Because of this flaw, an attacker could reuse an expired or otherwise invalid code to register their own passkey, thereby gaining unauthorized access to the victim's account.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to register a passkey on behalf of a victim by exploiting the improper expiration check. This means the attacker could gain unauthorized access to the victim's account, potentially compromising sensitive information and user identity within the ZITADEL identity management platform.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Zitadel to version 3.4.8 or 4.12.2 or later, where the issue with improper expiration check of the passkey registration code has been fixed.