Advisory

GHSA-pfrf-9r5f-73f5

Also known as: CVE-2026-29067, GO-2025-4212

Summary

ZITADEL Vulnerable to Account Takeover Due to Improper Instance Validation in V2 Login

Details

Summary

A potential vulnerability exists in ZITADEL's password reset mechanism in login V2. ZITADEL utilizes the Forwarded or X-Forwarded-Host header from incoming requests to construct the URL for the password reset confirmation link. This link, containing a secret code, is then emailed to the user.

Impact

If an attacker can manipulate these headers (e.g., via host header injection), they could cause ZITADEL to generate a password reset link pointing to a malicious domain controlled by the attacker. If the user clicks this manipulated link in the email, the secret reset code embedded in the URL can be captured by the attacker. This captured code could then be used to reset the user's password and gain unauthorized access to their account.

It's important to note that this specific attack vector is mitigated for accounts that have Multi-Factor Authentication (MFA) or Passwordless authentication enabled.

Affected Versions

Systems using the login UI (v2) and running one of the following versions are affected:

  • v4.x: 4.0.0-rc.1 through 4.7.0

Patches

The vulnerability has been addressed in the latest release. The patch resolves the issue by correctly validating the X-Forwarded-Host and Forwarded headers against the instance custom and trusted domains.

Before you upgrade, ensure that:

  • the ZITADEL_API_URL is set and is pointing to your instance, resp. system in multi-instance deployments.
  • the HTTP host (or a x-forwarded-host) is passed in your reverse proxy to the login UI.
  • a x-zitadel-instance-host (or x-zitadel-forward-host) is set in your reverse for multi-instance deployments. If you're running a single instance solution, you don't need to take any actions.

Patched versions:

Workarounds

The recommended solution is to update ZITADEL to a patched version.

A ZITADEL fronting proxy can be configured to delete all forwarded header values or set it to the requested host before sending requests to ZITADEL self-hosted environments.

Questions

If you have any questions or comments about this advisory, please email us at [[email protected]](mailto:[email protected])

Credits

Thanks to Amit Laish – GE Vernova for finding and reporting the vulnerability.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-12-08 22:19 UTC
Modified
2026-03-09 16:11 UTC

Affected packages and fixes

github.com/zitadel/zitadel

Go · All systems

Affected

  • introduced 0, fixed 1.80.0-v2.20.0.20251208091519-4c879b47334e (semver)

Fixed versions

1.80.0-v2.20.0.20251208091519-4c879b47334e

Fix

  • Fixed version 1.80.0-v2.20.0.20251208091519-4c879b47334e
    go get github.com/zitadel/[email protected]

github.com/zitadel/zitadel

Go · All systems

Affected

  • introduced 1.83.4, last affected 1.87.5 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

github.com/zitadel/zitadel

Go · All systems

Affected

  • introduced 4.0.0-rc.1, fixed 4.7.1 (semver)

Fixed versions

4.7.1

Fix

github.com/zitadel/zitadel/v2

Go · All systems

Affected

  • introduced 0, fixed 1.80.0-v2.20.0.20251208091519-4c879b47334e (semver)

Fixed versions

1.80.0-v2.20.0.20251208091519-4c879b47334e

Fix

  • Fixed version 1.80.0-v2.20.0.20251208091519-4c879b47334e
    go get github.com/zitadel/zitadel/[email protected]

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences