CVE-2025-67495: Github.com/zitadel/zitadel Cross-Site Scripting Vulnerability

HIGH
Advisory Identifier: GHSA-v959-qxv6-6f8p
CVSS 8.0
CWE-79
Published
Advisory Summary

CVE-2025-67495 is a HIGH (CVSS 8.0) cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting Github.com/zitadel/zitadel libraries in the Go ecosystem. The issue involves zitadel vulnerable to account takeover via dom-based xss in zitadel v2 login. Remediation is available by upgrading affected packages to version 1.80.0-v2.20.0.20251208091519-4c879b47334e, 4.7.1.

CVE-2025-67495 at a Glance

CVE Identifier CVE-2025-67495
GHSA Identifier GHSA-v959-qxv6-6f8p
Severity HIGH
CVSS v3.1 Base Score 8.0
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product Github.com/zitadel/zitadel
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2025-67495

To remediate this vulnerability, upgrade all affected Github.com/zitadel/zitadel dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/zitadel/zitadel fixed: 1.80.0-v2.20.0.20251208091519-4c879b47334e
Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20251208091519-4c879b47334e
github.com/zitadel/zitadel fixed: Latest secure release
Upgrade github.com/zitadel/zitadel to Latest secure release
github.com/zitadel/zitadel fixed: 4.7.1
Upgrade github.com/zitadel/zitadel to 4.7.1
github.com/zitadel/zitadel/v2 fixed: 1.80.0-v2.20.0.20251208091519-4c879b47334e
Upgrade github.com/zitadel/zitadel/v2 to 1.80.0-v2.20.0.20251208091519-4c879b47334e
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/zitadel/zitadel

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-67495, inspect your project dependencies for Github.com/zitadel/zitadel:

inspect dependencies for github.com/zitadel/zitadel

Analyze the terminal output to locate any version of Github.com/zitadel/zitadel in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.80.0-v2.20.0.20251208091519-4c879b47334e), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In Github.com/zitadel/zitadel, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary 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. ### Impact 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. ### 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 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](https://github.com/zitadel/zitadel/releases/tag/v4.7.1) ### 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 [security@zitadel.com](mailto:security@zitadel.com) ### Credits Thanks to Amit Laish – GE Vernova for finding and reporting the vulnerability.

CVE-2025-67495 Affected Github.com/zitadel/zitadel Versions

4 component(s)
Fixed Versions:
1.80.0-v2.20.0.20251208091519-4c879b47334e4.7.1
Product / Package Ecosystem Affected Versions Fixed Version
github.com/zitadel/zitadel
Go
< 1.80.0-v2.20.0.20251208091519-4c879b47334e
1.80.0-v2.20.0.20251208091519-4c879b47334e
github.com/zitadel/zitadel
Go
≥ 1.83.4
≤ 1.87.5
github.com/zitadel/zitadel
Go
≥ 4.0.0-rc.1
< 4.7.1
4.7.1
github.com/zitadel/zitadel/v2
Go
< 1.80.0-v2.20.0.20251208091519-4c879b47334e
1.80.0-v2.20.0.20251208091519-4c879b47334e

References

Frequently Asked Questions

What is CVE-2025-67495?
CVE-2025-67495 is a security vulnerability in Github.com/zitadel/zitadel involving ZITADEL Vulnerable to Account Takeover via DOM-Based XSS in Zitadel V2 Login under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which Github.com/zitadel/zitadel versions are affected?
Affected versions include releases prior to 1.80.0-v2.20.0.20251208091519-4c879b47334e, 4.7.1 across affected packages: github.com/zitadel/zitadel, github.com/zitadel/zitadel/v2.
What version fixes CVE-2025-67495?
Upgrading to 1.80.0-v2.20.0.20251208091519-4c879b47334e, 4.7.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/zitadel/zitadel affected?
Yes, github.com/zitadel/zitadel is affected in releases prior to 1.80.0-v2.20.0.20251208091519-4c879b47334e, Latest secure release, 4.7.1. Upgrade your dependency to 1.80.0-v2.20.0.20251208091519-4c879b47334e, Latest secure release, 4.7.1 or later.
Is github.com/zitadel/zitadel/v2 affected?
Yes, github.com/zitadel/zitadel/v2 is affected in releases prior to 1.80.0-v2.20.0.20251208091519-4c879b47334e. Upgrade your dependency to 1.80.0-v2.20.0.20251208091519-4c879b47334e or later.
What is the CVSS score of CVE-2025-67495?
CVE-2025-67495 has a CVSS v3.1 base score of 8.0 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N.
What CWE is associated with CVE-2025-67495?
CVE-2025-67495 is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.).
How can I check Go dependencies for CVE-2025-67495?
Run the dependency tree command: 'inspect dependencies for github.com/zitadel/zitadel'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-v959-qxv6-6f8p",
  "modified" : "2025-12-10T15:46:09Z",
  "published" : "2025-12-08T22:20:07Z",
  "aliases" : [ "CVE-2025-67495" ],
  "summary" : "ZITADEL Vulnerable to Account Takeover via DOM-Based XSS in Zitadel V2 Login",
  "details" : "### Summary\n\nA 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.\nZITADEL's login UI did not ensure that this parameter contained an allowed value and even executed passed scripts.\n\n### Impact\n\nZitadel 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.\n\nAn 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.\n\nNote 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.\n\n### Affected Versions\n\nSystems using the login UI (v2) and running one of the following versions are affected:\n- **v4.x**: `4.0.0-rc.1` through `4.7.0`\n\n### Patches\n\nThe 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).\nIf 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).\n\nBefore you upgrade, ensure that:\n- the `ZITADEL_API_URL` is set and is pointing to your instance, resp. system in multi-instance deployments.\n- the HTTP `host` (or a `x-forwarded-host`) is passed in your reverse proxy to the login UI.\n- 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.\n\nPatched versions:\n- 4.x: Upgrade to >=[4.7.1](https://github.com/zitadel/zitadel/releases/tag/v4.7.1)\n\n### Workarounds\n\nThe recommended solution is to update ZITADEL to a patched version.\n\n### Questions\n\nIf you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com)\n\n### Credits\n\nThanks to Amit Laish – GE Vernova for finding and reporting the vulnerability.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.80.0-v2.20.0.20251208091519-4c879b47334e"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.83.4"
      }, {
        "last_affected" : "1.87.5"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0-rc.1"
      }, {
        "fixed" : "4.7.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.80.0-v2.20.0.20251208091519-4c879b47334e"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/security/advisories/GHSA-v959-qxv6-6f8p"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-67495"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/commit/4c879b47334e01d4fcab921ac1b44eda39acdb96"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/zitadel/zitadel"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-12-08T22:20:07Z",
    "nvd_published_at" : "2025-12-09T23:15:59Z"
  }
}