ZITADEL is an open source identity management platform. From 4.0.0 until 4.16.1, ZITADEL Login V2 creates a browser session after password verification and can reuse that session for a later authentication request without verifying a user's enrolled TOTP, OTP, or U2F second factor. When the MFA step is abandoned and login starts again, session-validity checks require MFA only when the organization enables Force MFA or Force MFA for local users only, so a voluntarily enrolled factor can be skipped while completing an OIDC or SAML callback for a customer application. Login V1, the ZITADEL Console, Management and Admin APIs, and user self-management are not affected. This issue is fixed in version 4.16.1.
CVE-2026-85056
This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(low)
- EG Risk
- 41(Track)EG Risk 41/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity82% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 24, 2026
Last Modified
September 24, 2026
Advisory Details (4)
Auto-updated Sep 24, 2026v4.16.1
Patch available: zitadel/zitadel v4.16.1
https://github.com/zitadel/zitadel/releases/tag/v4.16.1commit 56f4798ed31f (zitadel/zitadel)
Fix landed in zitadel/zitadel commit 56f4798ed31f — awaiting tagged release
https://github.com/zitadel/zitadel/commit/56f4798ed31fc1cfcd9a0e7f6f0152289d2fdc43commit 049dbb25a565 (zitadel/zitadel)
Fix landed in zitadel/zitadel commit 049dbb25a565 — awaiting tagged release
https://github.com/zitadel/zitadel/commit/049dbb25a56587fb3980c85c99819cad69f637dbMFA bypass via session reuse in Login V2 · Advisory · zitadel/zitadel · GitHub
https://github.com/zitadel/zitadel/security/advisories/GHSA-9993-rfwp-rhwfVendor Advisories for CVE-2026-85056(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-24 18:35 UTCEG score recompute
- 2026-09-24 17:47 UTCEG score recompute
- 2026-09-24 17:46 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-85056?
When was CVE-2026-85056 disclosed?
What is the CVSS score of CVE-2026-85056?
How do I remediate CVE-2026-85056?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-85056
Is Your Infrastructure Affected by CVE-2026-85056?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.