CVE-2026-54693
Authorization bypass in ZITADEL lets users claim email/phone and bypass verification.
Is CVE-2026-54693 being exploited?
Not confirmed. CVE-2026-54693 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-54693?
CVE-2026-54693 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-54693?
Yes. A fix has been recorded for CVE-2026-54693. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54693 affect?
CVE-2026-54693 affects ZITADEL 2.43.0 through 2.71.19, ZITADEL 3.0.0 through 3.4.11, ZITADEL 4.0.0 through 4.15.1, internal/command/user_v2_email.go, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54693?
Upgrade to ZITADEL 3.4.11 or 4.15.1; disable self‑management endpoints and rotate affected credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can request verification codes without permission, claim email/phone ownership, bypass MFA/verification, enabling account takeover and privilege escalation.
Immediate action required
- affected>= 2.43.0 and <= 2.71.19
- affected>= 3.0.0-rc.1 and < 3.4.11
- affected>= 4.0.0-rc.1 and < 4.15.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.