# CVE-2026-119127: ZITADEL 4.0.0 before 4.19.5 Account Takeover via Login V2 Host Header Injection


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-47m4-8jqx-5r73, GHSA-mchc-246r-6m76

## What is CVE-2026-119127?

CVE-2026-119127 is a high-severity vulnerability in zitadel, published on 29 Oct 2026. 

### Official description

ZITADEL 4.0.0 before 4.19.5 contains a host header injection vulnerability in the Login V2 UI that allows unauthenticated attackers to poison password-reset, invite, and email-verification links by supplying untrusted x-zitadel-public-host, x-zitadel-forward-host, or x-forwarded-host headers. Attackers knowing a victim's login name can point the links in genuine emails at their host, harvest the single-use codes when the links are opened, and take over accounts including instance administrators.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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


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

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

## Is CVE-2026-119127 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119127 is a high-severity vulnerability in zitadel, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119127 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-119127/ (Markdown: https://insights.sbomify.com/CVE-2026-119127/index.md)
```

## Sources

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

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