ZITADEL Vulnerable to Account Takeover via Malicious Forwarded Header Injection

Exploitation

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

CVSS

8.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

EPSS

• CVE-2025-64101: 0.36% estimated exploitation activity in the next 30 days; percentile 30.17 (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.

Impact A potential vulnerability exists in ZITADEL's password reset mechanism. 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. 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 running one of the following versions: - 4.x: 4.0.0 to 4.5.0 (including RC…

Published by the source

29 Oct 2025, 22:20 UTC

Last modified by the source

5 Nov 2025, 22:13 UTC

Source last checked

26 Oct 2026, 15:13 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mwmh-7px9-4c23

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

# Patch Next advisory brief: CVE-2025-64101

Advisory: ZITADEL Vulnerable to Account Takeover via Malicious Forwarded Header Injection
IDs: CVE-2025-64101, GHSA-mwmh-7px9-4c23
Record: https://patchnext.com/advisories/cve-2025-64101 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/zitadel/zitadel/v2 2.71.18, 1.80.0-v2.20.0.20251029090537-72a5c33e6ac3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zitadel/zitadel/v2: affected >= 2.0.0, < 2.71.18; < 1.80.0-v2.20.0.20251029090537-72a5c33e6ac3; fixed in 1.80.0-v2.20.0.20251029090537-72a5c33e6ac3, 2.71.18

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/zitadel/zitadel/v2.
- 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://github.com/advisories/GHSA-mwmh-7px9-4c23 (GitHub-reviewed advisory GHSA-mwmh-7px9-4c23 lists affected ranges: Go github.com/zitadel/zitadel/v2 >=2.0.0 =0 <1.80.0-v2.20.0.20251029090537-72a5c33e6ac3)

Commands are suggestions: review each one before running it.