# CVE-2026-47194: Frappe: Host header poisoning can redirect magic login links to an attacker-controlled domain

> Attackers can poison the Host header to redirect magic login links to their domain, capturing tokens and potentially taking over user accounts.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-3w78-3cj3-p949

## What is CVE-2026-47194?

CVE-2026-47194 is a high-severity vulnerability in frappe, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Frappe is a full-stack web application framework. Prior to 15.108.0 and 16.18.3, temporary magic login link generation can use an attacker-controlled request Host header, allowing a remote attacker to cause emailed login links to point to an attacker-controlled domain and capture the login token when a recipient follows the link. This issue is fixed in versions 15.108.0 and 16.18.3.

Weakness: CWE-346 (Origin Validation Error)

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


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

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

## Is CVE-2026-47194 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47194 is a high-severity vulnerability in frappe, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-47194 in the wild and no public exploit code.

Affected product: frappe. 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-47194/ (Markdown: https://insights.sbomify.com/CVE-2026-47194/index.md)
```

## Sources

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

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