# CVE-2026-92816: ComfyUI before 0.30.0 Path Traversal via dataset save nodes

> Attackers can exploit unsanitized folder names in ComfyUI dataset save nodes to write files to arbitrary paths, potentially achieving code execution.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 16 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-xhvx-vf8p-rh4x

## What is CVE-2026-92816?

CVE-2026-92816 is a high-severity path traversal vulnerability in Comfy-Org ComfyUI, published on 16 Sep 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

ComfyUI before 0.30.0 fails to sanitize folder_name input in dataset save nodes, allowing attackers to write files to arbitrary paths outside the output directory. Attackers can load a crafted workflow that writes attacker-controlled content to arbitrary locations, enabling code execution through modified startup files or package initializers.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-92816 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92816 is a high-severity path traversal vulnerability in Comfy-Org ComfyUI, published on 16 Sep 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-92816 exists.

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

## Sources

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

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