VulnerabilityPublished 29 Oct 2025Updated 5 Nov 2025

CVE-2025-64101: V2 · ZITADEL Vulnerable to Account Takeover via Malicious Forwarded Header Injection

Affects github.com/zitadel/zitadel/v2Source GCVE Database

Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 2.71.18 soon.

Data as of 4 Nov 2026, 18:24 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 2.71.18, 1.80.0-v2.20.0.20251029090537-72a5c33e6ac3

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade github.com/zitadel/zitadel/v2 to 2.71.18; github.com/zitadel/zitadel/v2 to 1.80.0-v2.20.0.20251029090537-72a5c33e6ac3.

Affected software

Product	Affected	Fixed in
Gogithub.com/zitadel/zitadel/v2	Affected >=2.0.0 <2.71.18	Fixed in 2.71.18
Gogithub.com/zitadel/zitadel/v2	Affected <1.80.0-v2.20.0.20251029090537-72a5c33e6ac3	Fixed in 1.80.0-v2.20.0.20251029090537-72a5c33e6ac3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade ZITADEL to versions 2.71.18 or later, 3.4.3 or later, or 4.6.0 or later, which include proper validation of Forwarded and X-Forwarded-Host headers. Alternatively, configure a fronting proxy to strip these headers before requests reach ZITADEL in self-hosted environments. Enabling Multi-Factor Authentication or Passwordless authentication on user accounts also mitigates the risk of account takeover via this vulnerability.

Description

ZITADEL versions 2.0.0 through 2.71.17, 3.0.0 through 3.4.2, and 4.0.0 through 4.5.0 are vulnerable to an account takeover via malicious header injection. The vulnerability arises because ZITADEL uses the Forwarded or X-Forwarded-Host HTTP headers to build password reset confirmation links. An attacker who can manipulate these headers can cause the reset link to point to a malicious domain, capturing the secret reset code and potentially resetting the user's password. Accounts with Multi-Factor Authentication or Passwordless authentication are protected against this attack. Patched versions are available that validate these headers properly.

Impact

An attacker who can control or inject the Forwarded or X-Forwarded-Host headers can cause ZITADEL to send password reset links with secret codes pointing to attacker-controlled domains. If a user clicks such a link, the attacker can capture the reset code and reset the user's password, leading to account takeover. This vulnerability compromises confidentiality and integrity of user accounts but does not affect availability. Accounts protected by MFA or Passwordless authentication are not vulnerable to this attack vector.

Summary

This vulnerability (CVE-2025-64101) affects ZITADEL's password reset mechanism by allowing an attacker to manipulate the Forwarded or X-Forwarded-Host headers to generate password reset links pointing to attacker-controlled domains. The secret reset code embedded in these links can be intercepted by the attacker, enabling unauthorized account access. The attack is mitigated if the user account has MFA or Passwordless authentication enabled. The vulnerability affects ZITADEL versions 2.0.0 up to but not including 2.71.18, 3.0.0 up to but not including 3.4.3, and 4.0.0 up to but not including 4.6.0. Fixed versions properly validate these headers to prevent manipulation. A workaround includes configuring a fronting proxy to remove these headers before requests reach ZITADEL.

CWE-601URL Redirection to Untrusted Site (Open Redirect) (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
Use an intermediate disclaimer page that provides the user with a clear warning that they are leaving the current site. Implement a long timeout before the redirect occurs, or force the user to click on the link. Be careful to avoid XSS problems (CWE-79) when generating the disclaimer page.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.5 (opens in a new tab)
Attack patterns
Cross-Site Flashing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-640Weak Password Recovery Mechanism for Forgotten Password (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.
Architecture and Design
Make sure that all input supplied by the user to the password recovery mechanism is thoroughly filtered and validated.
Architecture and Design
Do not use standard weak security questions and use several security questions.
Architecture and Design
Make sure that there is throttling on the number of incorrect answers to a security question. Disable the password recovery functionality after a certain (small) number of incorrect guesses.
OWASP Cheat Sheets
Choosing and Using Security Questions (opens in a new tab)
Forgot Password (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.5.3 (opens in a new tab)
V2.5.2 (opens in a new tab)
V2.5.1 (opens in a new tab)
Attack patterns
Password Recovery Exploitation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 18:24 UTC

WeaknessesCWE-601, CWE-640

Technical details

References

Community reviews

Related threats