Is CVE-2026-105213 exploited in the wild?

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

How severe is CVE-2026-105213?

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

How is CVE-2026-105213 attacked?

It is attacked over the network.

Am I affected by CVE-2026-105213?

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-105213: ZITADEL authentication bypass via Login V2 for deactivated organizations

CVE-2026-105213 · Severity: high · CVSS 8.2 · Published 2026-10-04

ZITADEL is an identity and access management platform that controls user authentication and authorization. In affected versions, when an administrator deactivates an organization to prevent its users from logging in, the Login V2 authentication method fails to enforce this restriction. Attackers with valid credentials, existing sessions, or refresh tokens from a deactivated organization can still log in, create new sessions, and obtain or refresh tokens, potentially bypassing organizational access controls.

Technologies: ZITADEL. Vendors: ZITADEL.

Quick answers

Is CVE-2026-105213 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-105213 being exploited in the wild.
How severe is CVE-2026-105213?: High severity, with a CVSS score of 8.2, 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-105213?: Yes: fixed in 4.17.1. Until then: If an immediate upgrade is not possible, deactivate affected users individually (which is enforced), and review and revoke active sessions and outstanding refresh tokens for users in deactivated organizations. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-105213 attacked?: It is attacked over the network.
Am I affected by CVE-2026-105213?: 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

If an immediate upgrade is not possible, deactivate affected users individually (which is enforced), and review and revoke active sessions and outstanding refresh tokens for users in deactivated organizations.

Technical details

ZITADEL 4.0.0 through 4.17.0 do not verify an organization's inactive state during Login V2 authentication; only the individual user's status is checked. This is an improper authentication vulnerability (CWE-287) affecting the Login V2 flow specifically; the older Login V1 flow already blocks such access. An unauthenticated attacker on the network can exploit this without user interaction if they possess valid credentials or tokens from users in a deactivated organization. The fix in 4.17.1 enforces organization deactivation, invalidating existing sessions and tokens upon deactivation.

Affected products

ZITADEL ZITADEL 4.0.0 through 4.17.0

Timeline

2026-08-14: disclosed
2026-10-04: advisory
2026-10-04: patched: Version 4.17.1 released

References

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