CVE-2025-64103: Github.com/zitadel/zitadel/v2 Zitadel May Bypass Second Authentication Vulnerability

HIGH
Advisory Identifier: GHSA-cfjq-28r2-4jv5
CWE-287 CWE-308
Published
Advisory Summary

CVE-2025-64103 is a HIGH zitadel may bypass second authentication vulnerability (CWE-287: Improper Authentication) affecting Github.com/zitadel/zitadel/v2 libraries in the Go ecosystem. The issue involves zitadel may bypass second authentication factor. Remediation is available by upgrading affected packages to version 2.71.18, 1.80.0-v2.20.0.20251029091250-b284f8474eed.

CVE-2025-64103 at a Glance

CVE Identifier CVE-2025-64103
GHSA Identifier GHSA-cfjq-28r2-4jv5
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-287: Improper Authentication
Affected Product Github.com/zitadel/zitadel/v2
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2025-64103

To remediate this vulnerability, upgrade all affected Github.com/zitadel/zitadel/v2 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/v2 fixed: Latest secure release
Upgrade github.com/zitadel/zitadel/v2 to Latest secure release
github.com/zitadel/zitadel/v2 fixed: Latest secure release
Upgrade github.com/zitadel/zitadel/v2 to Latest secure release
github.com/zitadel/zitadel/v2 fixed: 2.71.18
Upgrade github.com/zitadel/zitadel/v2 to 2.71.18
github.com/zitadel/zitadel fixed: 1.80.0-v2.20.0.20251029091250-b284f8474eed
Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20251029091250-b284f8474eed
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/v2

How to Check if You Are Affected

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

inspect dependencies for github.com/zitadel/zitadel/v2

Analyze the terminal output to locate any version of Github.com/zitadel/zitadel/v2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.71.18), 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-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. In Github.com/zitadel/zitadel/v2, 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 vulnerability in Zitadel's token verification prematurely marked sessions as authenticated when only one factor was verified. ### Impact Zitadel provides an API for managing sessions, enabling custom login experiences in a dedicated UI or direct integration into applications. Session Tokens are issued for active sessions, which can be used as Bearer tokens to call the Zitadel API. Starting from 2.55.0 (see other affected versions below), Zitadel only required multi factor authentication in case the login policy has either enabled `requireMFA` or `requireMFAForLocalUsers`. If a user has set up MFA without this requirement, Zitadel would consider single factor auhtenticated sessions as valid as well and not require multiple factors. Bypassing second authentication factors weakens multifactor authentication and enables attackers to bypass the more secure factor. An attacker can target the TOTP code alone, only six digits, bypassing password verification entirely and potentially compromising accounts with 2FA enabled. ### Affected Versions Systems using the session API (v2 beta and v2) directly or via the new login UI in the following versions are affected: - **4.x**: `4.0.0` to `4.5.0` (including RC versions) - **3.x**: `3.0.0` to `3.4.2` (including RC versions) - **2.x**: `v2.53.6` to `v2.53.9`, `v2.54.3` to `v2.54.10`, `2.55.0` to `2.71.17` ### Patches The vulnerability has been addressed in the latest releases. The patch resolves the issue by requiring a configured second factor regardless of the login policies `requireMFA` or `requireMFAForLocalUsers` configuration. 4.x: Upgrade to >=[4.6.0](https://github.com/zitadel/zitadel/releases/tag/v4.6.0) 3.x: Update to >=[3.4.3](https://github.com/zitadel/zitadel/releases/tag/v3.4.3) 2.x: Update to >=[2.71.18](https://github.com/zitadel/zitadel/releases/tag/v2.71.18) ### 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 This vulnerability was found by [zentrust partners GmbH](https://zentrust.partners) during a scheduled penetration test. Thank you to the analysts Martin Tschirsich, Joud Zakharia, Christopher Baumann. The full report will be made public after the complete review.

CVE-2025-64103 Affected Github.com/zitadel/zitadel/v2 Versions

4 component(s)
Fixed Versions:
2.71.181.80.0-v2.20.0.20251029091250-b284f8474eed
Product / Package Ecosystem Affected Versions Fixed Version
github.com/zitadel/zitadel/v2
Go
≥ 2.53.6
≤ 2.53.9
github.com/zitadel/zitadel/v2
Go
≥ 2.54.3
≤ 2.54.10
github.com/zitadel/zitadel/v2
Go
≥ 2.55.0
< 2.71.18
2.71.18
github.com/zitadel/zitadel
Go
< 1.80.0-v2.20.0.20251029091250-b284f8474eed
1.80.0-v2.20.0.20251029091250-b284f8474eed

References

Frequently Asked Questions

What is CVE-2025-64103?
CVE-2025-64103 is a security vulnerability in Github.com/zitadel/zitadel/v2 involving Zitadel May Bypass Second Authentication Factor under CWE-287: Improper Authentication.
Which Github.com/zitadel/zitadel/v2 versions are affected?
Affected versions include releases prior to 2.71.18, 1.80.0-v2.20.0.20251029091250-b284f8474eed across affected packages: github.com/zitadel/zitadel/v2, github.com/zitadel/zitadel.
What version fixes CVE-2025-64103?
Upgrading to 2.71.18, 1.80.0-v2.20.0.20251029091250-b284f8474eed (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/zitadel/zitadel/v2 affected?
Yes, github.com/zitadel/zitadel/v2 is affected in releases prior to Latest secure release, 2.71.18. Upgrade your dependency to Latest secure release, 2.71.18 or later.
Is github.com/zitadel/zitadel affected?
Yes, github.com/zitadel/zitadel is affected in releases prior to 1.80.0-v2.20.0.20251029091250-b284f8474eed. Upgrade your dependency to 1.80.0-v2.20.0.20251029091250-b284f8474eed or later.
What CWE is associated with CVE-2025-64103?
CVE-2025-64103 is classified under CWE-287: Improper Authentication (When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.).
How can I check Go dependencies for CVE-2025-64103?
Run the dependency tree command: 'inspect dependencies for github.com/zitadel/zitadel/v2'. 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-cfjq-28r2-4jv5",
  "modified" : "2025-11-05T22:14:13Z",
  "published" : "2025-10-29T22:21:27Z",
  "aliases" : [ "CVE-2025-64103" ],
  "summary" : "Zitadel May Bypass Second Authentication Factor",
  "details" : "### Summary\n\nA vulnerability in Zitadel's token verification prematurely marked sessions as authenticated when only one factor was verified. \n\n### Impact\n\nZitadel provides an API for managing sessions, enabling custom login experiences in a dedicated UI or direct integration into applications. Session Tokens are issued for active sessions, which can be used as Bearer tokens to call the Zitadel API.\n\nStarting from 2.55.0 (see other affected versions below), Zitadel only required multi factor authentication in case the login policy has either enabled `requireMFA` or `requireMFAForLocalUsers`. If a user has set up MFA without this requirement, Zitadel would consider single factor auhtenticated sessions as valid as well and not require multiple factors.\n\nBypassing second authentication factors weakens multifactor authentication and enables attackers to bypass the more secure factor. An attacker can target the TOTP code alone, only six digits, bypassing password verification entirely and potentially compromising accounts with 2FA enabled.\n\n### Affected Versions\n\nSystems using the session API (v2 beta and v2) directly or via the new login UI in the following versions are affected:\n- **4.x**: `4.0.0` to `4.5.0` (including RC versions)\n- **3.x**: `3.0.0` to `3.4.2` (including RC versions)\n- **2.x**: `v2.53.6` to `v2.53.9`,  `v2.54.3` to `v2.54.10`, `2.55.0` to `2.71.17`\n\n### Patches\n\nThe vulnerability has been addressed in the latest releases. The patch resolves the issue by requiring a configured second factor regardless of the login policies `requireMFA` or `requireMFAForLocalUsers` configuration.\n\n4.x: Upgrade to >=[4.6.0](https://github.com/zitadel/zitadel/releases/tag/v4.6.0)\n3.x: Update to >=[3.4.3](https://github.com/zitadel/zitadel/releases/tag/v3.4.3)\n2.x: Update to >=[2.71.18](https://github.com/zitadel/zitadel/releases/tag/v2.71.18)\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\nThis vulnerability was found by [zentrust partners GmbH](https://zentrust.partners) during a scheduled penetration test. Thank you to the analysts Martin Tschirsich, Joud Zakharia, Christopher Baumann.\nThe full report will be made public after the complete review.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.53.6"
      }, {
        "last_affected" : "2.53.9"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.54.3"
      }, {
        "last_affected" : "2.54.10"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.55.0"
      }, {
        "fixed" : "2.71.18"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.71.17"
    }
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.80.0-v2.20.0.20251029091250-b284f8474eed"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/security/advisories/GHSA-cfjq-28r2-4jv5"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-64103"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/commit/b284f8474eed0cba531905101619e7ae7963156b"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/zitadel/zitadel"
  }, {
    "type" : "WEB",
    "url" : "https://pkg.go.dev/vuln/GO-2025-4083"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-287", "CWE-308" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-10-29T22:21:27Z",
    "nvd_published_at" : "2025-10-29T19:15:39Z"
  }
}