CVE-2026-85056 zitadel CVE debrief

Who should care

Defenders responsible for ZITADEL deployments, particularly those using Login V2, should assess exposure and prioritize upgrading to version 4.16.1. This includes reviewing organization settings for Force MFA or Force MFA for local users only and verifying MFA settings and user enrollment. Security teams and vulnerability management teams should also review the vulnerability and plan for remediation.

Why it matters

CVE-2026-85056 allows reused browser sessions without verifying second factors in ZITADEL Login V2, fixed in version 4.16.1. Defenders should verify exposure, review MFA settings, and upgrade.

• Potential unauthorized access to user accounts
• Need to verify MFA settings and user enrollment
• Possible session hijacking or reuse
• Requires review of organization settings for Force MFA

Technical summary

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. This allows for potential unauthorized access to user accounts and requires review of organization settings for Force MFA. The issue is fixed in version 4.16.1, and defenders should prioritize verifying exposure and upgrading to the latest version. Affected deployments should review compensating controls and verify MFA settings.

Defensive priority

Defenders should prioritize verifying exposure of ZITADEL Login V2 and upgrading to version 4.16.1.

Recommended defensive actions

• Verify exposure of ZITADEL Login V2
• Upgrade to version 4.16.1
• Review organization settings for Force MFA or Force MFA for local users only
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability and its fix. However, the corpus does not establish versions, exploitation, impact, or remediation beyond vendor-provided information.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.