CVE-2025-67495

A potential vulnerability exists in ZITADEL's logout endpoint in login V2. This endpoint accepts serval parameters including a post_logout_redirect. When this parameter is specified, users will be redirected to the site that is provided via this parameter.
ZITADEL's login UI did not ensure that this parameter contained an allowed value and even executed passed scripts.

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

Workarounds

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

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.

Zitadel is vulnerable to a DOM-Based XSS vulnerability. More specifically, the /logout endpoint insecurely routed to value that is supplied in the post_logout_redirect GET parameter. As a result, malicious JS code could be executed on Zitadel users’ browsers, in the Zitadel V2 Login domain.

An unauthenticated remote attacker can exploit this DOM-based XSS vulnerability, and thus, execute malicious JavaScript code on behalf of Zitadel users. By doing so, such an attacker could reset the password of their victims, and take over their accounts.

Note that for this to work, multiple user sessions need to be active in the same browser. Additionally, it's important to note that an account takeover is mitigated for accounts that have Multi-Factor Authentication (MFA) or Passwordless authentication enabled.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2025-67495 has a CVSS score of 8.0 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.80.0-v2.20.0.20251208091519-4c879b47334e, 4.7.1); upgrading removes the vulnerable code path.

Kodem intelligence

The vulnerability has been addressed in the latest release. The patch resolves the issue by ensuring the information was passed for the ZITADEL API using a JSON Web Token (JWT).
If you're running your own login UI, we recommend switching over to the new logout_token parameter, which contains all information previously passed via specific query parameters. The contained JWT's signature needs to be verified with the instance OAuth2/OIDC public keys (jwks_uri).

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

1. What is CVE-2025-67495? CVE-2025-67495 is a high-severity cross-site scripting (XSS) vulnerability in github.com/zitadel/zitadel (go), affecting versions < 1.80.0-v2.20.0.20251208091519-4c879b47334e. It is fixed in 1.80.0-v2.20.0.20251208091519-4c879b47334e, 4.7.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2025-67495? CVE-2025-67495 has a CVSS score of 8.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-67495?
   • github.com/zitadel/zitadel (go) (versions < 1.80.0-v2.20.0.20251208091519-4c879b47334e)
   • github.com/zitadel/zitadel/v2 (go) (versions < 1.80.0-v2.20.0.20251208091519-4c879b47334e)
4. Is there a fix for CVE-2025-67495? Yes. CVE-2025-67495 is fixed in 1.80.0-v2.20.0.20251208091519-4c879b47334e, 4.7.1. Upgrade to this version or later.
5. Is CVE-2025-67495 exploitable, and should I be worried? Whether CVE-2025-67495 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-67495 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-67495?
   • Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20251208091519-4c879b47334e or later
   • Upgrade github.com/zitadel/zitadel to 4.7.1 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 1.80.0-v2.20.0.20251208091519-4c879b47334e or later