# CVE-2026-105209: ZITADEL before 3.4.15 and 4.17.1 Cross-Organization Account Takeover via Passkey Enrollment

> Attackers with user-write permissions in one organization can take over accounts in other organizations by exploiting improper authorization in passkey enrollment.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-hcch-574x-xrm8, GHSA-pq2q-2c6r-75c4

## What is CVE-2026-105209?

CVE-2026-105209 is a critical missing authorization vulnerability in zitadel, published on 4 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ZITADEL 3.x before 3.4.15 and 4.x before 4.17.1 contains an improper authorization vulnerability: when issuing passkey or passwordless enrollment codes, it checks only the organization in the x-zitadel-orgid header, not the target user's organization. Attackers with user-write permission in one organization can obtain an enrollment code for a user in another organization on the same instance and register their own authenticator to take over that account.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-105209?


## How do I fix CVE-2026-105209?

No fix has been published for CVE-2026-105209 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105209 being exploited?

There is no known exploitation of CVE-2026-105209 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105209 and fix it if it is affected.

What it is: CVE-2026-105209 is a critical missing authorization vulnerability in zitadel, published on 4 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105209 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-105209/ (Markdown: https://insights.sbomify.com/CVE-2026-105209/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105209
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105209
- OSV: https://osv.dev/vulnerability/CVE-2026-105209

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105209/
Summaries are generated and may contain mistakes; the official description above is the record.