ZITADEL Users Can Self-Verify Email/Phone via API in github.com/zitadel/zitadel

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2026-54693: 0.58% estimated exploitation activity in the next 30 days; percentile 47.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

ZITADEL Users Can Self-Verify Email/Phone via API in github.com/zitadel/zitadel. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: .

Published by the source

29 Jul 2026, 16:54 UTC

Last modified by the source

18 Aug 2026, 15:00 UTC

Source last checked

25 Oct 2026, 04:53 UTC

1. Revision 3 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6141

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-jq8w-8q2f-ffm9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54693

Advisory: ZITADEL Users Can Self-Verify Email/Phone via API in github.com/zitadel/zitadel
IDs: CVE-2026-54693, GHSA-jq8w-8q2f-ffm9
Record: https://patchnext.com/advisories/cve-2026-54693 (revision 3, source checked 25 Oct 2026, 04:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: . A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zitadel/zitadel: affected every version; < 1.80.0-v2.20.0.20260608144108-ed09b3df7f43; fixed in 1.80.0-v2.20.0.20260608144108-ed09b3df7f43

## Suggested inspection (read-only)
- Go github.com/zitadel/zitadel: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/zitadel/zitadel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jq8w-8q2f-ffm9 (OSV record GHSA-jq8w-8q2f-ffm9 lists affected ranges: Go github.com/zitadel/zitadel >=4.0.0, >=2.43.0, >=0 <1.80.0-v2.20.0.20260608144108-ed09b3df7f43 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6141 (OSV record GO-2026-6141 lists affected ranges: Go github.com/zitadel/zitadel >=0, >=0 <1.80.0-v2.20.0.20260608144108-ed09b3df7f43 (fixed))

Commands are suggestions: review each one before running it.