How severe is GHSA-cfjq-28r2-4jv5?

No CVSS score has been assigned to GHSA-cfjq-28r2-4jv5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cfjq-28r2-4jv5?

GHSA-cfjq-28r2-4jv5 affects the following packages: github.com/zitadel/zitadel/v2 (Go), github.com/zitadel/zitadel/v2 (Go), github.com/zitadel/zitadel/v2 (Go), github.com/zitadel/zitadel (Go). Ecosystems affected: Go.

How do I fix GHSA-cfjq-28r2-4jv5?

A fix is available for GHSA-cfjq-28r2-4jv5; check the affected-versions list above or the advisory for the patched release of github.com/zitadel/zitadel/v2, then make sure no transitive dependency still pins the vulnerable range.

How do I detect GHSA-cfjq-28r2-4jv5 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zitadel/zitadel/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-cfjq-28r2-4jv5 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-cfjq-28r2-4jv5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-cfjq-28r2-4jv5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-cfjq-28r2-4jv5?

GHSA-cfjq-28r2-4jv5 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 29th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-cfjq-28r2-4jv5?

GHSA-cfjq-28r2-4jv5 is classified as Improper Authentication (CWE-287), CWE-308 (CWE-308). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cfjq-28r2-4jv5 published, and has it been updated?

GHSA-cfjq-28r2-4jv5 was published on October 29, 2025 and was last updated on November 5, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Zitadel May Bypass Second Authentication FactorGHSA-cfjq-28r2-4jv5

Fix: zitadel/zitadel@b284f84

GHSA-cfjq-28r2-4jv5 is a Improper Authentication vulnerability in github.com/zitadel/zitadel/v2. A fix is available for github.com/zitadel/zitadel/v2 — see the affected versions and patch details below.

Also known asCVE-2025-64103GO-2025-4083

Published

Oct 29, 2025

Updated

Nov 5, 2025

Affected

4 pkgs

Patched

2 / 4

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-cfjq-28r2-4jv5.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected

🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 3.x: Update to >=3.4.3 2.x: Update to >=2.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 [email protected]

Credits

This vulnerability was found by zentrust partners GmbH 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.

Affected Packages

4 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/zitadel/zitadel/v2`	≥ 2.53.6	No fix
🐹Go	`github.com/zitadel/zitadel/v2`	≥ 2.54.3	No fix
🐹Go	`github.com/zitadel/zitadel/v2`	≥ 2.55.0&&< 2.71.18	2.71.18`go get github.com/zitadel/zitadel/v2@v2.71.18`
🐹Go	`github.com/zitadel/zitadel`	all versions	1.80.0-v2.20.0.20251029091250-b284f8474eed`go get github.com/zitadel/zitadel@v1.80.0-v2.20.0.20251029091250-b284f8474eed`

Affected Products

1 product · 5 configurations

Application

zitadelzitadel

≥ 4.0.0 && ≤ 2.54.10

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zitadel/zitadel/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for GHSA-cfjq-28r2-4jv5; check the affected-versions list above or the advisory for the patched release of github.com/zitadel/zitadel/v2, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-cfjq-28r2-4jv5 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works