CVE-2026-54693

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

July 29, 2026

Last Modified

July 30, 2026

Advisory Details (6)

Auto-updated Jul 29, 2026
Patch available. Sources: github_commit, github_release, github.
github_release Patch Available

v4.15.1

Patch available: zitadel/zitadel v4.15.1

https://github.com/zitadel/zitadel/releases/tag/v4.15.1
github_release Patch Available

v3.4.11

Patch available: zitadel/zitadel v3.4.11

https://github.com/zitadel/zitadel/releases/tag/v3.4.11
github_commit

commit ed09b3df7f43 (zitadel/zitadel)

Fix landed in zitadel/zitadel commit ed09b3df7f43 — awaiting tagged release

https://github.com/zitadel/zitadel/commit/ed09b3df7f43e870423e4d8f2757e6894481604f
github_commit

commit a1748b2f0326 (zitadel/zitadel)

Fix landed in zitadel/zitadel commit a1748b2f0326 — awaiting tagged release

https://github.com/zitadel/zitadel/commit/a1748b2f0326ddf7be0de44b4f980ae2c07c0151
github_commit

commit 90f310212d3a (zitadel/zitadel)

Fix landed in zitadel/zitadel commit 90f310212d3a — awaiting tagged release

https://github.com/zitadel/zitadel/commit/90f310212d3a5075084a603bf61fed549c92956d
github Patch Available

Users Can Self-Verify Email/Phone via API · Advisory · zitadel/zitadel · GitHub

https://github.com/zitadel/zitadel/security/advisories/GHSA-jq8w-8q2f-ffm9

Vendor Advisories for CVE-2026-54693(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/zitadel/zitadel—1.80.0-v2.20.0.20260608144108-ed09b3df7f43—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-15 07:50 UTCEG score recompute
  2. 2026-09-15 03:11 UTCEPSS rescore
  3. 2026-09-14 03:11 UTCEG score recompute
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-13 01:23 UTCEG score recompute
  6. 2026-09-11 21:39 UTCEG score recompute
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-10 19:50 UTCEG score recompute
  9. 2026-09-10 09:35 UTCEPSS rescore
  10. 2026-09-09 07:47 UTCEG score recompute
  11. 2026-09-08 22:01 UTCEPSS rescore
  12. 2026-09-07 20:46 UTCEG score recompute
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 22:40 UTCEG score recompute
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-05 19:06 UTCEG score recompute
  17. 2026-09-05 05:10 UTCEG score recompute
  18. 2026-09-04 11:55 UTCEG score recompute
  19. 2026-09-04 05:06 UTCEPSS rescore
  20. 2026-09-02 14:12 UTCEPSS rescore
  21. 2026-09-01 22:46 UTCEG score recompute
  22. 2026-09-01 13:54 UTCEPSS rescore
  23. 2026-09-01 04:40 UTCEPSS rescore
  24. 2026-08-31 01:06 UTCEG score recompute
  25. 2026-08-30 19:17 UTCEPSS rescore
Show 59 more
  1. 2026-08-30 12:11 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-29 23:17 UTCEG score recompute
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 23:45 UTCEG score recompute
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 21:34 UTCEG score recompute
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 19:41 UTCEG score recompute
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-24 17:53 UTCEG score recompute
  12. 2026-08-23 02:18 UTCEG score recompute
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-22 00:23 UTCEG score recompute
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 11:28 UTCEG score recompute
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-19 20:28 UTCEG score recompute
  19. 2026-08-19 17:04 UTCEPSS rescore
  20. 2026-08-18 18:35 UTCEG score recompute
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-17 14:25 UTCEG score recompute
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-17 01:31 UTCEG score recompute
  25. 2026-08-16 14:56 UTCEPSS rescore
  26. 2026-08-16 12:37 UTCEG score recompute
  27. 2026-08-16 02:14 UTCEPSS rescore
  28. 2026-08-15 10:49 UTCEG score recompute
  29. 2026-08-15 01:30 UTCEPSS rescore
  30. 2026-08-14 09:00 UTCEG score recompute
  31. 2026-08-13 22:00 UTCEPSS rescore
  32. 2026-08-12 18:18 UTCEG score recompute
  33. 2026-08-12 13:51 UTCEPSS rescore
  34. 2026-08-11 16:25 UTCEG score recompute
  35. 2026-08-11 03:31 UTCEG score recompute
  36. 2026-08-11 00:00 UTCEPSS rescore
  37. 2026-08-10 01:43 UTCEG score recompute
  38. 2026-08-09 13:46 UTCEPSS rescore
  39. 2026-08-08 23:54 UTCEG score recompute
  40. 2026-08-08 16:37 UTCEPSS rescore
  41. 2026-08-07 22:05 UTCEG score recompute
  42. 2026-08-06 20:17 UTCEG score recompute
  43. 2026-08-06 13:47 UTCEPSS rescore
  44. 2026-08-06 07:23 UTCEG score recompute
  45. 2026-08-05 19:17 UTCEPSS rescore
  46. 2026-08-04 16:25 UTCEG score recompute
  47. 2026-08-04 15:10 UTCEPSS rescore
  48. 2026-08-04 10:39 UTCEPSS rescore
  49. 2026-08-03 14:36 UTCEG score recompute
  50. 2026-08-03 10:36 UTCEPSS rescore
  51. 2026-08-02 12:47 UTCEG score recompute
  52. 2026-08-02 02:27 UTCEPSS rescore
  53. 2026-08-01 10:59 UTCEG score recompute
  54. 2026-08-01 04:16 UTCEPSS rescore
  55. 2026-07-30 20:13 UTCEG score recompute
  56. 2026-07-30 16:28 UTCEPSS rescore
  57. 2026-07-29 17:26 UTCEG score recompute
  58. 2026-07-29 17:08 UTCEG score recompute
  59. 2026-07-29 17:07 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54693?
CVE-2026-54693 is a high vulnerability published on July 29, 2026. 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/userv2email.go, internal/command/userv2phone.go, and internal/command/userv2human.go allowed…
When was CVE-2026-54693 disclosed?
CVE-2026-54693 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54693 actively exploited?
CVE-2026-54693 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.5% of all scored CVEs.
What is the CVSS score of CVE-2026-54693?
CVE-2026-54693 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-54693?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54693, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54693

Explore →

Is Your Infrastructure Affected by CVE-2026-54693?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs