CVE-2026-105206 zitadel CVE debrief

Who should care

Defenders responsible for ZITADEL deployments, particularly those using versions 3.0.0 through 3.4.15 and 4.x before 4.17.3, should assess exposure and prioritize remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify affected deployments, monitor for suspicious activity, and upgrade to version 4.17.3 or later.

Why it matters

CVE-2026-105206 is a medium-severity vulnerability affecting ZITADEL, allowing authenticated members to learn about authentication method types used by users in other organizations. Defenders should prioritize verifying affected deployments, monitoring for suspicious activity, and upgrading to version 4.17.3 or later.

• Potential enumeration of authentication method types used by users in other organizations
• Possible exposure of user authentication information across organizations
• Verification of affected ZITADEL deployments and user authentication configurations
• Prioritization of upgrades to version 4.17.3 or later

Technical summary

The vulnerability is caused by an incorrect authorization flaw in the User Service API, which verifies user.read against the caller's organization rather than the organization owning the target user. This allows an authenticated member holding org-scoped user.read to query GET /v2/users/{userId}/authentication_methods to learn which authentication method types users in other organizations have registered.

Defensive priority

Defenders should prioritize verifying affected ZITADEL deployments and upgrading to version 4.17.3 or later. Inventory checks and monitoring for suspicious User Service API queries are recommended.

Recommended defensive actions

• Verify ZITADEL version and upgrade to 4.17.3 or later if affected
• Monitor User Service API queries for suspicious activity
• Perform inventory checks for affected deployments
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. However, additional information on exploitation or impact is limited. Defenders should verify affected deployments, monitor for suspicious activity, and review user authentication configurations. The vulnerability allows authenticated members to learn about authentication method types used by users in other organizations.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.