How severe is CVE-2026-29067?

CVE-2026-29067 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-29067?

CVE-2026-29067 affects the following packages: github.com/zitadel/zitadel (Go), github.com/zitadel/zitadel (Go), github.com/zitadel/zitadel (Go), github.com/zitadel/zitadel/v2 (Go). Ecosystems affected: Go.

How do I fix CVE-2026-29067?

Update github.com/zitadel/zitadel to 1.80.0-v2.20.0.20251208091519-4c879b47334e or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-29067 is resolved across your whole dependency graph.

How do I detect CVE-2026-29067 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zitadel/zitadel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-29067 if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is CVE-2026-29067 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-29067 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-29067?

CVE-2026-29067 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-29067?

CVE-2026-29067 is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-29067 published, and has it been updated?

CVE-2026-29067 was published on March 7, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2026-29067 — zitadel

HIGHFix: zitadel/zitadel@4c879b4

CVE-2026-29067 is a high-severity (CVSS 8.1) Open Redirect vulnerability in github.com/zitadel/zitadel. A fix is available for github.com/zitadel/zitadel — see the affected versions and patch details below.

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

Also known asGHSA-pfrf-9r5f-73f5GO-2025-4212

Published

Mar 7, 2026

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

3 / 4

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-29067.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadel/v2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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:

4.x: Upgrade to >=4.7.1

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]

Credits

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

Affected Packages

4 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/zitadel/zitadel`	all versions	1.80.0-v2.20.0.20251208091519-4c879b47334e`go get github.com/zitadel/zitadel@v1.80.0-v2.20.0.20251208091519-4c879b47334e`
🐹Go	`github.com/zitadel/zitadel`	≥ 1.83.4	No fix
🐹Go	`github.com/zitadel/zitadel`	≥ 4.0.0-rc.1&&< 4.7.1	4.7.1`go get github.com/zitadel/zitadel@v4.7.1`
🐹Go	`github.com/zitadel/zitadel/v2`	all versions	1.80.0-v2.20.0.20251208091519-4c879b47334e`go get github.com/zitadel/zitadel/v2@v1.80.0-v2.20.0.20251208091519-4c879b47334e`

Affected Products

1 product · 1 configurations

Application

zitadelzitadel

≥ 4.0.0 && < 4.7.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zitadel/zitadel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/zitadel/zitadel to 1.80.0-v2.20.0.20251208091519-4c879b47334e or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-29067 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

### 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 embedd