Skip to main content
VulnerabilityPublished

CVE-2026-105211: ZITADEL before 4.17.1 contains an authentication bypass vulnerability in Login V2 that allows unauthenticated attackers to take over accounts by

Affects zitadelSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 4.17.1 soon.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.17.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade zitadel/zitadel to 4.17.1.

Affected software

ProductAffectedFixed in
GitHubzitadel/zitadelpkg:github/zitadel/zitadelOther threatsAffected
  • <4.17.1
Fixed in
  • 4.17.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in ZITADEL version 4.17.1. Users should upgrade to version 4.17.1 or later to remediate this vulnerability. No other mitigation guidance is provided, and patching is the recommended course of action.

Description

ZITADEL versions before 4.17.1 have an authentication bypass vulnerability in the Login V2 component. This flaw allows unauthenticated attackers to take over accounts by exploiting the returnCode delivery type to obtain OTP codes. Attackers who know a victim's login name and that the victim has OTP-Email and OTP-SMS enrolled can read both OTP codes from server responses, enabling them to gain MFA-authenticated sessions, including administrator accounts.

References

Community reviews

Loading reviews…