# CVE-2025-48936: ZITADEL Allows Account Takeover via Malicious X-Forwarded-Proto Header Injection > Attackers can manipulate headers to redirect password reset links, capturing secret codes to take over user accounts without MFA. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 30 May 2025 - **Updated:** 30 May 2025 - **Also known as:** GHSA-93m4-mfpg-c3xf, GO-2025-3721 ## What is CVE-2025-48936? CVE-2025-48936 is a high-severity vulnerability in zitadel, published on 30 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Zitadel is open-source identity infrastructure software. Prior to versions 2.70.12, 2.71.10, and 3.2.2, a potential vulnerability exists in the 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. This specific attack vector is mitigated for accounts that have Multi-Factor Authentication (MFA) or Passwordless authentication enabled. This issue has been patched in versions 2.70.12, 2.71.10, and 3.2.2. Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-601 (URL Redirection to Untrusted Site) ## Which versions are affected by CVE-2025-48936? 11 open source packages ship an affected version, including github.com/zitadel/zitadel/v2 and github.com/zitadel/zitadel. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/zitadel/zitadel/v2` | Go | All versions | None | | `github.com/zitadel/zitadel/v2` | Go | All versions | None | | `github.com/zitadel/zitadel/v2` | Go | From 2.38.3 | 2.70.12 | | `github.com/zitadel/zitadel/v2` | Go | From 2.38.3 | 2.70.12 | | `github.com/zitadel/zitadel/v2` | Go | From 2.71.0 | 2.71.11 | | `github.com/zitadel/zitadel/v2` | Go | From 2.71.0 | 2.71.11 | | `github.com/zitadel/zitadel/v2` | Go | From 3.0.0-rc1 | 3.2.2 | | `github.com/zitadel/zitadel/v2` | Go | From 3.0.0-rc1 | 3.2.2 | | `github.com/zitadel/zitadel` | Go | All versions | 0.0.0-20250528081227-c097887bc5f6 | | `github.com/zitadel/zitadel` | Go | All versions | 0.0.0-20250528081227-c097887bc5f6 | | `github.com/zitadel/zitadel` | Go | All versions | 0.0.0-20250528081227-c097887bc5f6 | Products: Zitadel Zitadel. ## How do I fix CVE-2025-48936? Upgrade github.com/zitadel/zitadel/v2 to a fixed version for your release line: 2.70.12, 2.71.11 or 3.2.2. ## Is CVE-2025-48936 being exploited? There is no known exploitation of CVE-2025-48936 in the wild and no public exploit code. ## Other vulnerabilities in zitadel - [CVE-2026-29191](https://insights.sbomify.com/CVE-2026-29191/): ZITADEL: 1-Click Account Takeover via XSS in /saml-post Endpoint (critical 9.3) - [CVE-2025-67494](https://insights.sbomify.com/CVE-2025-67494/): ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login (critical 9.3) - [CVE-2025-27507](https://insights.sbomify.com/CVE-2025-27507/): IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations (critical 9.0) - [CVE-2025-64103](https://insights.sbomify.com/CVE-2025-64103/): Zitadel Bypass Second Authentication Factor (high 8.7) - [CVE-2025-31123](https://insights.sbomify.com/CVE-2025-31123/): Zitadel Expired JWT Keys Usable for Authorization Grants (high 8.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-48936 and fix it if it is affected. What it is: CVE-2025-48936 is a high-severity vulnerability in zitadel, published on 30 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2025-48936 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/zitadel/zitadel/v2 (Go): affected all versions; no fix listed - github.com/zitadel/zitadel/v2 (Go): affected all versions; no fix listed - github.com/zitadel/zitadel/v2 (Go): affected from 2.38.3; fixed in 2.70.12 - github.com/zitadel/zitadel/v2 (Go): affected from 2.38.3; fixed in 2.70.12 - github.com/zitadel/zitadel/v2 (Go): affected from 2.71.0; fixed in 2.71.11 - github.com/zitadel/zitadel/v2 (Go): affected from 2.71.0; fixed in 2.71.11 - github.com/zitadel/zitadel/v2 (Go): affected from 3.0.0-rc1; fixed in 3.2.2 - github.com/zitadel/zitadel/v2 (Go): affected from 3.0.0-rc1; fixed in 3.2.2 - github.com/zitadel/zitadel (Go): affected all versions; fixed in 0.0.0-20250528081227-c097887bc5f6 - github.com/zitadel/zitadel (Go): affected all versions; fixed in 0.0.0-20250528081227-c097887bc5f6 - github.com/zitadel/zitadel (Go): affected all versions; fixed in 0.0.0-20250528081227-c097887bc5f6 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-48936/ (Markdown: https://insights.sbomify.com/CVE-2025-48936/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-48936 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-48936 - OSV: https://osv.dev/vulnerability/CVE-2025-48936 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-48936/ Summaries are generated and may contain mistakes; the official description above is the record.