Is CVE-2026-105211 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-105211 being exploited in the wild.

How severe is CVE-2026-105211?

High severity, with a CVSS score of 8.1, published 4 October 2026.

How is CVE-2026-105211 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-105211?

Check whether you run ZITADEL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-105211: ZITADEL authentication bypass in Login V2 OTP handling

CVE-2026-105211 · Severity: high · CVSS 8.1 · Published 2026-10-04

ZITADEL is an identity and access management platform that handles user authentication and account management. An unauthenticated attacker who knows a user's login name can fully take over that account—including administrator accounts—by exploiting a flaw in the Login V2 interface that reveals one-time passwords for email and SMS second factors. The attacker gains unauthorized access without needing the user's password or any security keys.

Technologies: ZITADEL. Vendors: ZITADEL.

Quick answers

Is CVE-2026-105211 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-105211 being exploited in the wild.
How severe is CVE-2026-105211?: High severity, with a CVSS score of 8.1, published 4 October 2026.
Which products and versions are affected?: ZITADEL 4.0.0 through 4.17.0.
Is there a fix for CVE-2026-105211?: Yes: fixed in 4.17.1. Until then: Avoid enrolling both OTP-Email and OTP-SMS on the same account, especially for privileged users such as IAM_OWNER roles; prefer TOTP, U2F/security keys, or passkeys as second factors instead. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-105211 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-105211?: Check whether you run ZITADEL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 4.17.1

Avoid enrolling both OTP-Email and OTP-SMS on the same account, especially for privileged users such as IAM_OWNER roles; prefer TOTP, U2F/security keys, or passkeys as second factors instead.

Technical details

The vulnerability is an improper authentication bypass in Login V2's server actions, where the returnCode delivery type for OTP challenges exposes generated codes directly in HTTP responses instead of sending them out-of-band. An unauthenticated attacker can submit both OTP-Email and OTP-SMS codes obtained from these responses to create an MFA-authenticated session, since the backend incorrectly counted two second factors as satisfying MFA without requiring a primary authentication factor. The attack succeeds only against victims with both OTP factors enrolled and active; it was fixed in 4.17.1 by removing returnCode exposure in the frontend, enforcing primary authentication at the backend, and redefining MFA to require a primary plus secondary factor.

Affected products

ZITADEL ZITADEL 4.0.0 through 4.17.0

Timeline

2026-08-14: disclosed
2026-10-04: advisory
2026-10-04: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.