Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

ZITADEL Login V2 OTP Bypass (CVE-2026-105211)

CVE-2026-105211 is an authentication bypass in ZITADEL's hosted Login V2.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-105211
Vendor
ZITADEL
Affected Product
ZITADEL hosted Login V2
Exploitation
Not confirmed
Published
2026-10-04

ZITADEL says an unauthenticated attacker who knows a login name can take over an account when both OTP-Email and OTP-SMS are already enrolled.The flaw exposes generated one-time codes before primary authentication and then counts two second factors as sufficient multi-factor authentication. The vendor published GHSA-3gwm-5wx8-4gm6 on August 14, 2026. VulnCheck's CNA record assigned the CVE on October 4, 2026.

What it allows

How Does CVE-2026-105211 Bypass Login V2 MFA?

ZITADEL says Login V2 forwarded browser-originated OTP challenge requests to the backend before a primary factor was verified. A delivery mode returned generated email and SMS codes in the server response rather than sending them to the account owner.

The attacker could submit both codes, and ZITADEL counted the two second factors as a completed MFA session. That session could access the account through ZITADEL APIs. An administrator account could expose the entire instance; an ordinary account would expose that user's access.

The affected path reuses factors already enrolled on the account. The vendor distinguishes it from a separate enrollment flaw described in another advisory. For wider triage, see the vulnerability intelligence platform alongside the identity-service inventory.

How Should Teams Prioritize This ZITADEL Flaw?

The October 5 CISA ADP record marked its exploitation assessment as none. CVE-2026-105211 was absent from CISA KEV catalog version 2026.11.13. Neither record establishes that vulnerable deployments are safe.

Brandefense Blackhole counted three dark-chat posts mentioning this CVE from August 17 through November 15, 2026. A GitHub repository-name search on November 15 found one public repository naming the CVE. These separate signals may overlap and do not prove an incident or active exploitation.

Evidence as of November 15
Exploit signals
  • CISA KEVNot seenNot listed in catalog 2026.11.132026-11-13
  • Brandefense BlackholeYesThree dark-chat mentions, not incidents2026-11-15
  • GitHub searchYesOne public repository naming this CVE, code unverified2026-11-15
  • Active exploitationUnknownThese signals do not prove exploitation2026-11-15
Verdict Activity unverified

Prioritize the fix by checking reachable Login V2 deployments and accounts with both OTP factors. The CISA KEV catalog is one input, while exposure and privileged-account impact matter here even without a KEV listing.

Who is affected

Version Check

ZITADEL
Release LineAffected RangeFixed In
4.x4.0.0 to before 4.17.14.17.1
Release ranges source

For distribution packages and custom builds, check the supplier’s advisory.

ZITADEL includes 4.x release candidates in the affected range. Check prerelease builds manually and verify the version actually running on each instance.

Which ZITADEL Versions and Configurations Are Affected?

ZITADEL lists 4.0.0 through 4.17.0, including release candidates, as affected. Its 4.17.1 release contains the fix. The CNA record uses a broader machine-readable range below 4.17.1; the vendor's explicit 4.x range guides this profile.

The account must already have both OTP-Email and OTP-SMS enrolled and ready. The instance must allow both factors in its login policy and have an SMS provider configured. Applications using ZITADEL's hosted Login V2 for OIDC or SAML sign-in are in scope.

Inventory ZITADEL instances, installed releases, Login V2 use, login policies, SMS-provider configuration, and privileged accounts with both OTP factors. Use the what vulnerability prioritization means context to schedule exposed identity systems first.

How Should Defenders Verify the Fix?

Upgrade affected 4.x deployments to ZITADEL 4.17.1 or a later patched release. After maintenance, confirm the running service reports the intended version on every instance and that Login V2 authentication works for its applications.

ZITADEL says the patch removes the browser-facing code-return option, requires a primary factor before that option can be used in the backend, and changes MFA evaluation. On an unpatched deployment, avoiding simultaneous OTP-Email and OTP-SMS enrollment can reduce exposure, but ZITADEL says no configuration fully closes the flaw.

Timeline

  1. 2026-08-14

    ZITADEL published advisory GHSA-3gwm-5wx8-4gm6 and named 4.17.1 as the patched release.

  2. 2026-10-04

    VulnCheck published CVE-2026-105211 and referenced the earlier ZITADEL advisory.

What to do

  1. Find affected identity systems

    Inventory ZITADEL instances running hosted Login V2 and identify 4.x releases before 4.17.1. Check whether connected OIDC or SAML applications use that sign-in path.

  2. Identify the required factor combination

    Check login policy, SMS provider configuration, and accounts with both OTP-Email and OTP-SMS enrolled. Prioritize privileged accounts and reachable production deployments.

  3. Upgrade and verify the running release

    Apply ZITADEL 4.17.1 or a later patched release. Confirm the version reported by every running instance after maintenance, then check Login V2 sign-in for connected applications.

  4. Review suspicious sessions

    As a Brandefense defensive recommendation, review authentication and session records for unexpected access to accounts that met the factor conditions. Investigate privileged sessions first.

What Brandefense can do

Frequently Asked Questions

What is CVE-2026-105211?

It is a ZITADEL Login V2 authentication bypass involving already enrolled OTP-Email and OTP-SMS factors. An attacker with the account's login name could obtain an MFA-authenticated session.

Which release fixes CVE-2026-105211?

ZITADEL says 4.17.1 fixes the issue. Its advisory lists 4.0.0 through 4.17.0, including release candidates, as affected.

Why does the ZITADEL advisory say no known CVE?

The advisory was published on August 14, 2026. VulnCheck assigned CVE-2026-105211 on October 4 and linked that advisory. The two records describe the same flaw.

Has active exploitation of CVE-2026-105211 been established?

The CISA ADP assessment from October 5 marked exploitation as none. Three Brandefense Blackhole dark-chat mentions and one GitHub search result are signals, not evidence of successful exploitation.

Sources

  1. Unauthenticated account takeover via OTP-Email and OTP-SMS return-code bypass in Login V2ZITADEL
  2. CVE-2026-105211 RecordVulnCheck CNA via CVE Program
  3. Known Exploited Vulnerabilities CatalogCISA
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →