Quick answers
- Is CVE-2026-105212 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105212 being exploited in the wild.
- How severe is CVE-2026-105212?
- High severity, with a CVSS score of 7.5, published 4 October 2026.
- Which products and versions are affected?
- ZITADEL 3.0.0 to 3.4.13, 4.0.0 to 4.16.1.
- Is there a fix for CVE-2026-105212?
- Yes: fixed in ZITADEL 3.4.14, 4.16.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105212 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-105212?
- 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: ZITADEL 3.4.14, 4.16.2
Technical details
ZITADEL's hosted Login V1 and Login V2 UIs accept authenticator (passkey) enrollment on identify-only login sessions—after a username is submitted but before primary factor verification. An unauthenticated attacker knowing only a valid username can enroll an attacker-controlled authenticator and complete login, circumventing password and MFA requirements. The vulnerability stems from missing authentication checks before allowing authenticator enrollment within the login flow.
Affected products
- ZITADEL ZITADEL 3.0.0 to 3.4.13, 4.0.0 to 4.16.1
Timeline
- 2026-07-29: disclosed
- 2026-10-04: advisory