Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54693

Authorization Flaw in github.com/zitadel/zitadel (CVE-2026-54693)

Summary

Vulnerability in github.com/zitadel/zitadel (CVE-2026-54693). Risk of unauthorized operations or information disclosure. Exploitable via UpdateHumanUser. Mitigation: upgrade to 1.80.0-v2.20.0.20260608144108-ed09b3df7f43 or later.

Original description

The description as published by the source.

Summary

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.

Impact

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.

Note that when changing another user's email or phone, regardless of the verification flag, the permissions were correctly checked.

Affected Versions

Systems running one of the following versions are affected:

  • 4.x: 4.0.0 through 4.15.0 (including RC versions)
  • 3.x: 3.0.0 through 3.4.10 (including RC versions)
  • 2.x: 2.43.0 through 2.71.19

Patches

The vulnerability has been addressed in the latest releases. The patch resolves the issue by requiring the correct permission…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54693 has been found in github.com/zitadel/zitadel.
Attackers can target a specific entry point like UpdateHumanUser over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20260608144108-ed09b3df7f43 or later.
If unsure, ask your IT team or search "github.com/zitadel/zitadel CVE-2026-54693" on the vendor's site.

CVE-2026-54693 (github.com/zitadel/zitadel) — CWE-863
Attack surface: UpdateHumanUser
Patched: 1.80.0-v2.20.0.20260608144108-ed09b3df7f43 — apply immediately
Workaround: The recommended solution is to upgrade to a patched version.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Incorrect authorization (CWE-863) exists in github.com/zitadel/zitadel. Attackers reach the vulnerable code path via UpdateHumanUser.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/zitadel/zitadel. Attack surface: UpdateHumanUser.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.80.0-v2.20.0.20260608144108-ed09b3df7f43.

🛡️ Workaround

Workaround: The recommended solution is to upgrade to a patched version.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/zitadel/zitadel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/zitadel/zitadel' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/zitadel/zitadel を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    The recommended solution is to upgrade to a patched version.

    パッチが適用されるまでの応急処置として、The recommended solution is to upgrade to a patched version. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20260608144108-ed09b3df7f43

    ステージング環境で 1.80.0-v2.20.0.20260608144108-ed09b3df7f43 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/zitadel/zitadel
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.80.0-v2.20.0.20260608144108-ed09b3df7f43"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details