MFA bypass via password-verified session reuse
Published Sep 24, 2026 · Updated Sep 24, 2026
Authentication bypass in ZITADEL 4.0.0 through 4.16.0 allows remote attackers with valid credentials to complete OIDC or SAML login without MFA. Login V2 creates a browser session after password verification, then reuses it without checking a voluntarily enrolled TOTP, OTP, or U2F factor. The bypass requires valid credentials, an enrolled factor, and a policy that does not force MFA; it grants access only to customer applications using Login V2.
Summary
What happened
Authentication bypass in ZITADEL 4.0.0 through 4.16.0 allows remote attackers with valid credentials to complete OIDC or SAML login without MFA. Login V2 creates a browser session after password verification, then reuses it without checking a voluntarily enrolled TOTP, OTP, or U2F factor. The bypass requires valid credentials, an enrolled factor, and a policy that does not force MFA; it grants access only to customer applications using Login V2.
The record
- CVE
- CVE-2026-85056
- Published
- Sep 24, 2026
- Updated
- Sep 24, 2026
- Vendor
- ZITADEL
- Product
- ZITADEL
- Classifications
- T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 24, 2026CVE publishedPublication date reported by the CVE source.
- Sep 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 4.0.0, < 4.16.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started