Servers and applications
GHSA-558c-v5wc-9w4q
Users in deactivated organizations can still log in with Login V2
- Severity
- High 8.2
- Published
- 14 Aug 2026
- Last changed
- 14 Aug 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 4.17.1
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Read some data · Change data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N- Sources
- Project advisories (GitHub)
Description
In ZITADEL, deactivating an organization is meant to stop its users from logging in. With Login V2 enabled, that was not always enforced. Users in a deactivated organization could still sign in, create sessions, and obtain or refresh tokens.
When an administrator deactivates an organization, ZITADEL’s documentation and Console both state that users of that organization will no longer be able to log in.
In affected versions, the organization’s inactive state was not checked during Login V2 authentication. Only the individual user’s status was checked. As a result, users in a deactivated organization could continue to authenticate if they still had valid credentials, or an existing session or refresh token.
Scope note: This affects applications that use Login V2 for end-user authentication. The older Login V1 flow already blocks users in deactivated organizations. In affected versions, sessions and tokens created before deactivation may still work until they expire.
Workarounds
The recommended solution is to upgrade to a patched version.
If an immediate upgrade is not possible, deactivate affected users individually. User deactivation is enforced and will prevent login.
You should also review active sessions for users in the organization and revoke or wait out any outstanding refresh tokens.
Affected software
| Software | Affected versions |
|---|---|
ZITADELServers and applications · github:zitadel/zitadel |
|
About ZITADEL
ZITADEL - Identity infrastructure, simplified for you.
- GitHub stars
- 15,585GitHub, 15 Nov 2026
- Forks
- 1,432GitHub, 15 Nov 2026
- Latest release
- v4.20.3GitHub, 15 Nov 2026
- Released
- 13 Nov 2026GitHub
- License
- AGPL-3.0GitHub
- First published on GitHub
- 16 Mar 2020GitHub
Vulnerabilities in ZITADEL
- In our list
- 103
- Published in the last 12 months
- 72
- Critical, last 12 months
- 13
- High, last 12 months
- 37
- Known exploited
- 0
- GHSA-qqv8-37gw-ww2qMissing second-factor check on authenticator enrollment in Login V2 (MFA bypass)High 8.1 18 Nov 2026
- GHSA-vg5j-vf6h-586mLogin V2 exposes internal functions as unauthenticated endpointsHigh 7.4 13 Nov 2026
- GHSA-3gwf-ph53-v73cLogin V2: authentication bypass via unauthenticated (zero-factor) session for OIDC and SAML requestsHigh 7.4 13 Nov 2026
- GHSA-gx82-3gqq-j4h5Session API and Login V2: organization login policy not enforced for password sign-inHigh 7.1 13 Nov 2026
- GHSA-fphg-99ff-7qrpLogin V2: external IdP sign-in callback not bound to the initiating browser (login CSRF / session swapping)Medium 5.4 13 Nov 2026
- GHSA-pm3x-9hh8-g745Login V2: Arbitrary Redirect URL AcceptedMedium 4.3 13 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-558c-v5wc-9w4q
- github.com https://github.com/zitadel/zitadel/security/advisories/GHSA-558c-v5wc-9w4q