ZITADEL Users Can Self-Verify Email/Phone via API (CVE-2026-54693)
A vulnerability in Zitadel's user self-management API allowed users to mark their email and phone as verified without completing the actual verification process. This was due to improper permission checks that enabled users to retrieve verification codes for email and phone numbers they do not control. The issue affects Zitadel versions 4.0.0 through 4.15.0, 3.0.0 through 3.4.10, and 2.43.0 through 2.71.19. The vulnerability has been fixed in versions 4.15.1 and later, 3.4.11 and later, and 3.4.11 and later for the respective branches. Users are advised to upgrade to these patched versions to mitigate the risk. If upgrading is not possible, a workaround exists to prevent returning verification codes to the user.
AI Analysis
Technical Summary
Zitadel's self-management API had a permission bypass vulnerability (CWE-863) that allowed authenticated users to self-verify email addresses and phone numbers by obtaining verification codes without proper authorization. Although prior fixes addressed the ability to mark arbitrary emails or phones as verified via the UpdateHumanUser API, this additional path allowed users to claim ownership of contact information they do not control, potentially bypassing email-based security policies. The vulnerability affects multiple major versions of Zitadel and has been remediated by enforcing correct permission checks and restricting self-management to the user's own email and phone only.
Potential Impact
Exploiting this vulnerability allows a user to bypass email and phone verification controls by self-verifying contact information without actual ownership. This could undermine security policies relying on verified contact details, potentially leading to unauthorized account recovery or access scenarios. The impact is limited to the user's own account, as permission checks prevent modifying other users' contact verification status.
Mitigation Recommendations
A fix is available and has been released in Zitadel versions 4.15.1 and 3.4.11 and later. Users should upgrade to these patched versions to resolve the vulnerability. If upgrading is not immediately possible, a workaround involves configuring an action (v2) to prevent returning verification codes to the user. No other mitigation steps are recommended beyond applying the official patch or workaround.
ZITADEL Users Can Self-Verify Email/Phone via API (CVE-2026-54693)
Description
A vulnerability in Zitadel's user self-management API allowed users to mark their email and phone as verified without completing the actual verification process. This was due to improper permission checks that enabled users to retrieve verification codes for email and phone numbers they do not control. The issue affects Zitadel versions 4.0.0 through 4.15.0, 3.0.0 through 3.4.10, and 2.43.0 through 2.71.19. The vulnerability has been fixed in versions 4.15.1 and later, 3.4.11 and later, and 3.4.11 and later for the respective branches. Users are advised to upgrade to these patched versions to mitigate the risk. If upgrading is not possible, a workaround exists to prevent returning verification codes to the user.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Zitadel's self-management API had a permission bypass vulnerability (CWE-863) that allowed authenticated users to self-verify email addresses and phone numbers by obtaining verification codes without proper authorization. Although prior fixes addressed the ability to mark arbitrary emails or phones as verified via the UpdateHumanUser API, this additional path allowed users to claim ownership of contact information they do not control, potentially bypassing email-based security policies. The vulnerability affects multiple major versions of Zitadel and has been remediated by enforcing correct permission checks and restricting self-management to the user's own email and phone only.
Potential Impact
Exploiting this vulnerability allows a user to bypass email and phone verification controls by self-verifying contact information without actual ownership. This could undermine security policies relying on verified contact details, potentially leading to unauthorized account recovery or access scenarios. The impact is limited to the user's own account, as permission checks prevent modifying other users' contact verification status.
Mitigation Recommendations
A fix is available and has been released in Zitadel versions 4.15.1 and 3.4.11 and later. Users should upgrade to these patched versions to resolve the vulnerability. If upgrading is not immediately possible, a workaround involves configuring an action (v2) to prevent returning verification codes to the user. No other mitigation steps are recommended beyond applying the official patch or workaround.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-jq8w-8q2f-ffm9
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-54693"]
- Ecosystems
- ["Go"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a6ae54b9c2644c7f89887ab
Added to database: 07/30/2026, 05:46:51 UTC
Last enriched: 07/30/2026, 07:19:36 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.