# CVE-2026-54693: ZITADEL Users Can Self-Verify Email/Phone via API

> Attackers can bypass email or phone verification checks to claim ownership of unverified contact details, potentially bypassing security policies.

- **Severity:** High 8.2 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-jq8w-8q2f-ffm9, GO-2026-6141

## What is CVE-2026-54693?

CVE-2026-54693 is a high-severity missing authorization vulnerability in zitadel, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

ZITADEL is an open source identity management platform. From 2.43.0 through 2.71.19, from 3.0.0 until 3.4.11, and from 4.0.0 until 4.15.1, the email and phone self-management API paths in internal/command/user_v2_email.go, internal/command/user_v2_phone.go, and internal/command/user_v2_human.go allowed users to request returned verification codes without the required permission, allowing users to claim ownership of email addresses or phone numbers they do not control and bypass email-based or phone-based security policies. This issue is fixed in versions 3.4.11 and 4.15.1.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-54693?

8 open source packages ship an affected version, including github.com/zitadel/zitadel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/zitadel/zitadel` | Go | All versions | None |
| `github.com/zitadel/zitadel` | Go | All versions | 1.80.0-v2.20.0.20260608144108-ed09b3df7f43 |
| `github.com/zitadel/zitadel` | Go | All versions | 1.80.0-v2.20.0.20260608144108-ed09b3df7f43 |
| `github.com/zitadel/zitadel` | Go | All versions | 1.80.0-v2.20.0.20260608144108-ed09b3df7f43 |
| `github.com/zitadel/zitadel` | Go | From 2.43.0 | None |
| `github.com/zitadel/zitadel` | Go | From 2.43.0 | None |
| `github.com/zitadel/zitadel` | Go | From 4.0.0 | None |
| `github.com/zitadel/zitadel` | Go | From 4.0.0 | None |

## How do I fix CVE-2026-54693?

Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20260608144108-ed09b3df7f43 or later.

## Is CVE-2026-54693 being exploited?

There is no known exploitation of CVE-2026-54693 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54693 and fix it if it is affected.

What it is: CVE-2026-54693 is a high-severity missing authorization vulnerability in zitadel, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-54693 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/zitadel/zitadel (Go): affected all versions; no fix listed
- github.com/zitadel/zitadel (Go): affected all versions; fixed in 1.80.0-v2.20.0.20260608144108-ed09b3df7f43
- github.com/zitadel/zitadel (Go): affected all versions; fixed in 1.80.0-v2.20.0.20260608144108-ed09b3df7f43
- github.com/zitadel/zitadel (Go): affected all versions; fixed in 1.80.0-v2.20.0.20260608144108-ed09b3df7f43
- github.com/zitadel/zitadel (Go): affected from 2.43.0; no fix listed
- github.com/zitadel/zitadel (Go): affected from 2.43.0; no fix listed
- github.com/zitadel/zitadel (Go): affected from 4.0.0; no fix listed
- github.com/zitadel/zitadel (Go): affected from 4.0.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54693/ (Markdown: https://insights.sbomify.com/CVE-2026-54693/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54693
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54693
- OSV: https://osv.dev/vulnerability/CVE-2026-54693

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54693/
Summaries are generated and may contain mistakes; the official description above is the record.