Servers and applications
CVE-2026-54693
Users Can Self-Verify Email/Phone via API
- Severity
- High 8.2
- Published
- 8 Jun 2026
- Last changed
- 15 Jun 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 3.4.11, 4.15.1
- Exploit chance
- 0.6% in the next 30 daysHigher than 48% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · Needs someone to click or open something
- Attacker can
- Change data
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N- Also known as
- GHSA-jq8w-8q2f-ffm9
- Sources
- Project advisories (GitHub)
Description
A vulnerability in Zitadel's self-management capability allowed users to mark their email and phone as verified without going through an actual verification process.
While GHSA-282g-fhmx-xf54 (CVE-2026-27946, "Users Can Self-Verify Email/Phone via UpdateHumanUser API") closed the path that let any authenticated user mark an arbitrary email or phone as verified on their own account by calling UpdateHumanUser with email.is_verified: true, additional paths were discovered.
Zitadel provides an API for managing users. The API also allows users to self-manage their own data including updating the email and phone.
Due to an improper permission check, the API allowed returning the verification code for the email and phone to the own user. This allows users to claim ownership of an email or phone they do not control and potentially bypass email-based security policies.
Workarounds
The recommended solution is to upgrade to a patched version. If an upgrade is not possible, an action (v2) could be used to prevent returning the verification code to the own user.
Affected software
| Software | Affected versions |
|---|---|
ZITADELServers and applications · github:zitadel/zitadel |
|
About ZITADEL
ZITADEL - Identity infrastructure, simplified for you.
- GitHub stars
- 15,585GitHub, 15 Nov 2026
- Forks
- 1,432GitHub, 15 Nov 2026
- Latest release
- v4.20.3GitHub, 15 Nov 2026
- Released
- 13 Nov 2026GitHub
- License
- AGPL-3.0GitHub
- First published on GitHub
- 16 Mar 2020GitHub
Vulnerabilities in ZITADEL
- In our list
- 103
- Published in the last 12 months
- 72
- Critical, last 12 months
- 13
- High, last 12 months
- 37
- Known exploited
- 0
- GHSA-qqv8-37gw-ww2qMissing second-factor check on authenticator enrollment in Login V2 (MFA bypass)High 8.1 18 Nov 2026
- GHSA-vg5j-vf6h-586mLogin V2 exposes internal functions as unauthenticated endpointsHigh 7.4 13 Nov 2026
- GHSA-3gwf-ph53-v73cLogin V2: authentication bypass via unauthenticated (zero-factor) session for OIDC and SAML requestsHigh 7.4 13 Nov 2026
- GHSA-gx82-3gqq-j4h5Session API and Login V2: organization login policy not enforced for password sign-inHigh 7.1 13 Nov 2026
- GHSA-fphg-99ff-7qrpLogin V2: external IdP sign-in callback not bound to the initiating browser (login CSRF / session swapping)Medium 5.4 13 Nov 2026
- GHSA-pm3x-9hh8-g745Login V2: Arbitrary Redirect URL AcceptedMedium 4.3 13 Nov 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-54693
- GitHub Advisory Database https://github.com/advisories/GHSA-jq8w-8q2f-ffm9
- github.com https://github.com/zitadel/zitadel/security/advisories/GHSA-jq8w-8q2f-ffm9