CVE-2026-105213 ZITADEL before 4.17.1 Authentication Bypass via Login V2 for Deactivated Organizations
High 8.8
Published
Updated
Check this codebase for CVE-2026-105213 and fix it if it is affected.
What it is: CVE-2026-105213 is a high-severity vulnerability in zitadel, published on 4 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-105213 in the wild and no public exploit code.
Affected product: zitadel. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-105213/ (Markdown: https://insights.sbomify.com/CVE-2026-105213/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-105213?
CVE-2026-105213 is a high-severity vulnerability in zitadel, published on 4 Oct 2026.
Official description
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.
Weakness: CWE-287
Which versions are affected by CVE-2026-105213?
How do I fix CVE-2026-105213?
No fix has been published for CVE-2026-105213 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-105213 being exploited?
There is no known exploitation of CVE-2026-105213 in the wild and no public exploit code.
Sources
Also known as GHSA-3fc9-77fj-j3c7, GHSA-558c-v5wc-9w4q.