cve.bz

CVE-2025-64103 zitadel zitadel: Improper Authentication

8.7 highEPSS 0.4%Fix available

High (8.7) in zitadel zitadel. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/zitadel/zitadel/v2 2.71.18.

On this page
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.

Severity

CVSS 4.0

8.7 high
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

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2025-10-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-287 Improper Authentication
CWE-308 Use of Single-factor Authentication
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-64103 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-64103?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-64103?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-64103 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
zitadel:zitadelfrom 2.53.6 through 2.53.9
zitadel:zitadelfrom 2.54.3 through 2.54.10
zitadel:zitadelfrom 2.55.0 before 2.71.18
zitadel:zitadelfrom 3.0.0 before 3.4.3
zitadel:zitadelfrom 4.0.0 before 4.6.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-cfjq-28r2-4jv5Gogithub.com/zitadel/zitadel/v2>=2.53.6 <=2.53.9no fix published
GHSA-cfjq-28r2-4jv5Gogithub.com/zitadel/zitadel/v2>=2.54.3 <=2.54.10no fix published
GHSA-cfjq-28r2-4jv5Gogithub.com/zitadel/zitadel/v2>=2.55.0 <2.71.182.71.18
GHSA-cfjq-28r2-4jv5Gogithub.com/zitadel/zitadel<1.80.0-v2.20.0.20251029091250-b284f8474eed1.80.0-v2.20.0.20251029091250-b284f8474eed
GO-2025-4083Gogithub.com/zitadel/zitadelall versionsno fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1
openSUSETumbleweedgovulncheck-vulndb0.0.20251105T184115-1.1openSUSE-SU-2025:15710-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-308 (14).

References

Check your stackJSON