CVE-2025-64103 json
Zitadel Bypass Second Authentication Factor
published 2025-10-29 12 mo ago modified 2026-10-19 20 d ago also EUVD-2025-36696 , GHSA-cfjq-28r2-4jv5 , GO-2025-4083
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
Starting from 2.53.6, 2.54.3, and 2.55.0, 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. This vulnerability is fixed in 4.6.0, 3.4.3, and 2.71.18.
Patch / fix
- go github.com/zitadel/zitadel/v2 2.71.18
- go github.com/zitadel/zitadel 1.80.0-v2.20.0.20251029091250-b284f8474eed
- zitadel zitadel 2.71.18, 3.4.3, 4.6.0
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
- govulncheck-vulndb openSUSE Tumbleweed 0.0.20251105T184115-1.1
opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2025:15710-1
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 12 mo ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.7 | 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 |
| CNA | 4.0 | 8.7 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/zitadel/zitadel/v2 | >=2.53.6, <=2.53.9 >=2.54.3, <=2.54.10 >=2.55.0, <2.71.18 |
2.71.18 |
| go | github.com/zitadel/zitadel | <1.80.0-v2.20.0.20251029091250-b284f8474eed all versions |
1.80.0-v2.20.0.20251029091250-b284f8474eed |
Affected products
- zitadel zitadel
Classification
References
-
github.com
/zitadel/zitadel/commit/b284f8474eed0cba531905101619e7ae7963156b
web, patch
-
github.com
/zitadel/zitadel/security/advisories/GHSA-cfjq-28r2-4jv5
web, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-64103
advisory
-
github.com
/zitadel/zitadel
package
-
pkg.go.dev
/vuln/GO-2025-4083
web
Sources
- CVE List CVE-2025-64103
- GitHub Advisory GHSA-cfjq-28r2-4jv5
- NVD CVE-2025-64103
- OSV GO-2025-4083
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.