# CVE-2026-67179: Genkit improper host header validation

> Attackers on the local network or via DNS rebinding can execute arbitrary Genkit actions and read results on the Dev UI server.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-vj3w-h7v3-5rpr

## What is CVE-2026-67179?

CVE-2026-67179 is a high-severity missing authorization vulnerability in genkit-ai genkit, published on 11 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Genkit does not properly validate host request headers. Any host on the developer's network, and any website the developer visits (via DNS rebinding), can reach POST /api/runAction on the Dev UI server (default port 4000) and execute any registered Genkit action and read the result. Fixed on 2026-06-18.

Weakness: CWE-644 (Improper Neutralization of HTTP Headers for Scripting Syntax)

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


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

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

## Is CVE-2026-67179 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67179 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67179 is a high-severity missing authorization vulnerability in genkit-ai genkit, published on 11 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67179 exists.

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

## Sources

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

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