Back Redpacketsecurity CVE Alert: CVE-2026-105213 – zitadel
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. Users of a deactivated organization who hold valid credentials, an existing session, or a refresh token can still sign in, create sessions, and obtain or refresh tokens.
**Risk verdict:** Treat this as a high-priority authentication weakness; exploitation urgency cannot be confirmed because KEV, SSVC, PoC and EPSS data were not provided.
**Why this matters:** Continued access after an organisation is deactivated can defeat an intended access cutoff, exposing its data and enabling unauthorised changes in connected services. The main concern is integrity and access to protected information, rather than service disruption; valid credentials or existing tokens make former users a realistic risk.
**Most likely attack path:** The login flow is network-reachable and requires neither prior privileges nor user interaction, with no special attack condition indicated. An attacker with valid credentials, a live session or a refresh token could obtain continued access; the flaw does not itself imply a boundary crossing, though applications that trust issued tokens may be affected.
**Who is most exposed:** Deployments using this identity platform for workforce, customer or partner sign-in are exposed, especially where organisation deactivation is relied upon to revoke access promptly.
Alert on successful login or token refresh for an organisation marked inactive.
Review session and token issuance after organisation deactivation.
Correlate identity events with downstream application access and writes.
Mitigation and prioritisation
Upgrade to the vendor-fixed release; confirm the deployed Login V2 path is covered.
Revoke sessions and refresh tokens associated with deactivated organisations.
Until patched, block or disable Login V2 access for affected organisations where feasible.
Test deactivation and token-revocation behaviour in staging, then schedule a prompt production change; if KEV is true or EPSS is at least 0.5, treat as priority 1.
A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.
If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
