Skip to main content
VulnerabilityPublished

CVE-2026-105213: ZITADEL 4.x before 4.17.1 does not check an organization's inactive state during Login V2 authentication, verifying only the individual user's status

Affects zitadelSource GCVE Database

0
Compare

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

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% 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:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade zitadel/zitadel to 4.17.1.

Affected software

ProductAffectedFixed in
GitHubzitadel/zitadelpkg:github/zitadel/zitadelOther threatsAffected
  • >=4.0.0 <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 ensure that the organization's inactive state is properly checked during Login V2 authentication, preventing users from deactivated organizations from authenticating.

Description

ZITADEL versions 4.x prior to 4.17.1 do not verify whether an organization is inactive during Login V2 authentication, only checking the individual user's status. This allows users belonging to deactivated organizations who have valid credentials, existing sessions, or refresh tokens to continue signing in, creating sessions, and obtaining or refreshing tokens.

References

Community reviews

Loading reviews…