CVE-2026-109371 zitadel CVE debrief

Who should care

Defenders responsible for ZITADEL deployments, particularly those using version 3.0.0 before 4.18.0, should assess exposure and prioritize upgrading to version 4.18.0 or later. They should also review login flows for potential vulnerabilities, monitor for suspicious login activity, and verify system upgrades. Affected operators, platforms, vulnerability-management, and security teams should be aware of the potential impacts and take necessary actions.

Why it matters

Defenders should care about CVE-2026-109371 because it allows unauthenticated attackers to change usernames in ZITADEL deployments, potentially disrupting login flows and locking out administrators. Affected deployments should prioritize upgrading to version 4.18.0 or later and review login flows for vulnerabilities. Evidence is limited, and further verification is needed to determine the full scope of affected systems and potential exploitation.

• Potential for unauthorized username changes
• Lockout of administrators and users
• Possible disruption of login flows
• Need for verification of system upgrades

Technical summary

ZITADEL 3.0.0 before 4.18.0 contains a missing authentication vulnerability in the hosted Login V1 UI, allowing unauthenticated attackers to submit a victim's login name and post a new username to rename any active human user, including administrators. This vulnerability can disrupt login flows and lock out administrators. Affected deployments should prioritize upgrading to version 4.18.0 or later and review login flows for vulnerabilities. Evidence is limited, and further verification is needed to determine the full scope of affected systems and potential exploitation.

Defensive priority

Defenders should prioritize verifying and upgrading to version 4.18.0 or later, and review login flows for potential vulnerabilities.

Recommended defensive actions

• Verify and upgrade to version 4.18.0 or later
• Review login flows for potential vulnerabilities
• Monitor for suspicious login activity
• 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
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance

Evidence notes

The CVE record and source item provide details on the vulnerability, but limited information is available on exploitation or affected systems. Defenders should verify and upgrade to version 4.18.0 or later, review login flows for potential vulnerabilities, and monitor for suspicious login activity. Further verification is needed to determine the full scope of affected systems and potential exploitation.

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.