Skip to content
,

ComfyUI-Easy-Use Vulnerability (CVE-2026-123790): How to Check, Fix and Lock Down ComfyUI

8–12 minutes
Woman in a home office holding a card reading EASY-USE, hook patch this ComfyUI node now

If you use ComfyUI-Easy-Use, one of the most popular ComfyUI node packs, update it today. On 12 November 2026, the US CERT Coordination Center published advisory VU#944667 (CVE-2026-123790).

It covers a flaw that lets anyone who can reach your ComfyUI server run their own code on your machine, with no password and no click from you.

This guide explains who is at risk, how to check your version, how to apply the fix, how to look for signs that someone already used it, and how to lock ComfyUI down so the next bug like this cannot reach you.

TL;DR

  • Affected: ComfyUI-Easy-Use 1.4.1 and earlier (the CVE record lists 1.3.6 to 1.4.1).
  • Risk: an attacker uploads a Python file, then abuses the save_preview() route to copy it over another custom node’s __init__.py. It runs the next time ComfyUI restarts.
  • Who is exposed: anyone whose ComfyUI can be reached by other people: --listen on a network, cloud GPU pods, shared or public URLs. A default local install on 127.0.0.1 is much safer, but still update.
  • Fix: update to the latest code on the main branch, which includes fix commit 8a0f2fc412. No numbered release was listed when I checked, so verify the commit (steps below).
  • Can’t update? CERT says remove the extension or limit network access to trusted users.

New to ComfyUI? My ComfyUI beginner guide covers install, models, nodes and fixes in one place.

What Happened

ComfyUI-Easy-Use (by yolain, about 2,700 GitHub stars) adds simplified loaders, samplers and many helper nodes, so it is installed on a huge number of ComfyUI setups.

Item Detail
Advisory CERT/CC VU#944667
CVE CVE-2026-123790 (CWE-22, path traversal)
Published 12 November 2026
Maintainer told 6 October 2026 (per CERT)
Affected versions 1.4.1 and earlier
Vulnerable route POST /easyuse/save/{name}, handled by save_preview()
Login needed? No
User click needed? No
Fix Commit 8a0f2fc412 on main (“fix: harden model metadata and preview routes”)
Severity score Not yet assigned (NVD analysis pending)
Reported by Nguyen Huy Hoang

CERT notes the maintainer could not be reached to coordinate the advisory, but the fix is already in the repository.

How the Attack Works

In plain words:

  1. ComfyUI lets anyone who can reach it upload files into its input folder. That is normal; it is how you load images.
  2. The attacker uploads a Python file there, disguised as something harmless.
  3. They call Easy-Use’s preview-saving route. In vulnerable versions it does not check the file name and target properly, so it can be told to copy that file into the custom_nodes folder, over another node pack’s __init__.py.
  4. The next time ComfyUI starts, it imports every custom node, so the attacker’s code runs.

That code runs with the same rights as ComfyUI. CERT says it can run system commands, read or change your models, workflows and other files, and grab any credentials in ComfyUI’s environment, such as API keys or cloud tokens.

Am I at Risk?

Your setup Risk Why
ComfyUI Desktop or portable, default settings, used only on your PC Low It listens on 127.0.0.1, so other machines cannot reach it. Update anyway.
Started with --listen or --listen 0.0.0.0 on home Wi-Fi Medium Anyone on your network (guests, a hacked smart device) can reach it.
Port 8188 forwarded on your router, or a tunnel (ngrok, Cloudflare Tunnel) without a login High Anyone on the internet can reach it.
Cloud GPU pod (RunPod, Vast.ai and similar) with a public ComfyUI URL High Public URLs get scanned. Add auth or close the port.
Shared studio or classroom server Medium-High Every user on the network can reach it.

Even “low risk” is not zero: a malicious web page or another compromised app on your PC could still talk to localhost. Updating takes two minutes, so do it.

Check Your Easy-Use Version

Option 1: ComfyUI Manager

  1. Open Manager, then Custom Nodes Manager.
  2. Set the filter to Installed and search for Easy-Use.
  3. Look at the version shown. 1.4.1 or lower means you need the fix.

Option 2: Git (most reliable)

Because the fix landed as a commit on main rather than a numbered release, the best test is whether your copy contains that commit. Open a terminal in the node folder:

cd ComfyUI/custom_nodes/ComfyUI-Easy-Use
git fetch origin
git merge-base --is-ancestor 8a0f2fc412 HEAD && echo "FIXED" || echo "NOT FIXED - update now"

On Windows PowerShell, run the same commands from ComfyUI\custom_nodes\ComfyUI-Easy-Use, and replace the last line with:

git merge-base --is-ancestor 8a0f2fc412 HEAD; if ($?) { "FIXED" } else { "NOT FIXED - update now" }

If the folder is not a git repository (you installed from a zip), treat it as not fixed and reinstall it.

How to Fix It

Fix 1: Update with git (recommended)

cd ComfyUI/custom_nodes/ComfyUI-Easy-Use
git checkout main
git pull
git merge-base --is-ancestor 8a0f2fc412 HEAD && echo "FIXED"

Then restart ComfyUI and hard-refresh the browser (Ctrl+F5), because the fix also updates Easy-Use’s front-end files.

Fix 2: Update from ComfyUI Manager

  1. In Custom Nodes Manager, find ComfyUI-Easy-Use and click Try update (or Switch Ver and choose nightly).
  2. Restart ComfyUI.
  3. Run the git check above to confirm. A “latest” numbered version may still be 1.4.1 or older, which would not include the fix.

Fix 3: Remove it

If you do not use its nodes, or you cannot update right now, CERT’s advice is to remove it:

  1. Stop ComfyUI.
  2. Delete or move the folder ComfyUI/custom_nodes/ComfyUI-Easy-Use out of custom_nodes.
  3. Start ComfyUI. Workflows that used Easy-Use nodes will show them in red until you reinstall the fixed version.

Using Comfy Desktop? Custom nodes live in the ComfyUI folder you chose at install, under custom_nodes. Need a refresher on updating? See my guide to updating ComfyUI and ComfyUI Manager setup.

Check for Signs of a Break-In

If your ComfyUI was reachable from a network while you ran an old Easy-Use, take five minutes to check. Nothing here is proof on its own, but these are the traces this attack leaves.

1. Python files in the input folder

The attacker needs to upload a script first. Normal use only puts images, videos and audio there.

# Linux / macOS
find ComfyUI/input -type f -name "*.py"

# Windows PowerShell
Get-ChildItem ComfyUI\input -Recurse -Filter *.py

2. Changed __init__.py files in other node packs

Most node packs are git clones, so git can tell you if a tracked file was changed locally:

# Linux / macOS, from the ComfyUI folder
for d in custom_nodes/*/; do
  (cd "$d" && git status --short 2>/dev/null | grep -q . && echo "Local changes: $d")
done
# Windows PowerShell, from the ComfyUI folder
Get-ChildItem custom_nodes -Directory | ForEach-Object {
  if (Test-Path "$($_.FullName)\.git") {
    $s = git -C $_.FullName status --short
    if ($s) { "Local changes: $($_.Name)"; $s }
  }
}

For any pack it flags, run git diff inside it. An __init__.py you never edited that now contains unknown code is a red flag. Also sort __init__.py files by modified date and look for any changed on a day you did not update.

3. If you find something

  • Stop ComfyUI and take it off the network.
  • Do not just delete the file and carry on. The code may already have run and planted something else.
  • Rotate every key the machine could see: Hugging Face, Civitai, OpenAI or other API keys, cloud tokens, SSH keys.
  • For a cloud pod, destroy it and start a fresh one from a clean template.
  • For a home PC, run a full antivirus scan and consider a clean reinstall of ComfyUI in a new folder, moving only your models and workflows across.

Our breach checklist has more detail on rotating keys after a leak.

Lock Down ComfyUI

This will not be the last security bug in a ComfyUI node pack. These habits stop most of them from reaching you:

  1. Do not use --listen unless you need it. Without it, ComfyUI only answers your own PC.
  2. Never forward port 8188 on your router. For remote access use a VPN such as Tailscale or WireGuard, so only your devices can reach it.
  3. Put a login in front of shared or cloud setups. A reverse proxy (Caddy, nginx) with a password, or a tunnel with access control, keeps strangers out.
  4. Keep the Manager security level at normal or strong on any machine others can reach. See our ComfyUI security level guide.
  5. Install fewer node packs. Every pack adds routes to the server. Remove the ones you do not use.
  6. Update node packs monthly, not only ComfyUI itself.
  7. Keep secrets out of ComfyUI’s environment where you can. Do not leave long-lived cloud keys in environment variables on a shared box.

What the Fix Changes

The fix commit (8a0f2fc412, “harden model metadata and preview routes”) goes beyond the single bug. Based on the commit:

  • Preview saving: previews can only come from ComfyUI’s temp folder, must be a plain file name with an image extension, must pass an image check with Pillow, and symlinks are rejected.
  • Model names: metadata and notes routes accept only checkpoints, LoRAs and embeddings that ComfyUI already knows about.
  • Hashes: model hashes are now computed from the file itself, not trusted from a .sha256 sidecar file.
  • Reboot route: changed from GET to POST, needs a token and rejects cross-site requests.
  • Tests: a new security test file covers scripts disguised as images, custom-node targets, symlink tricks and forged hashes.

Because the front-end changed too, always restart ComfyUI and refresh the browser after updating.

Troubleshooting

Problem Fix
git pull says “local changes would be overwritten” Run git status first. If you did not make those changes, they may be the attack (see above). If you did, run git stash, then git pull.
fatal: not a git repository It was installed from a zip. Delete the folder and reinstall with git clone https://github.com/yolain/ComfyUI-Easy-Use or through Manager.
merge-base says “Not a valid commit name” Run git fetch origin first so your copy knows about the new commit.
Manager shows no update Use Switch Ver, then nightly, or update with git.
Easy-Use buttons misbehave after update Hard-refresh the browser (Ctrl+F5) to load the new front-end.
“Reboot” from Easy-Use stopped working The reboot route now needs a token and POST. Update the front-end (refresh) or restart ComfyUI normally.
Workflows show red Easy-Use nodes after removal Expected. Reinstall the fixed version, or swap them for core nodes.

FAQ

Is ComfyUI itself vulnerable?

This advisory is about the ComfyUI-Easy-Use custom node pack, not ComfyUI core. But the attack uses ComfyUI’s normal upload feature as its first step, so network exposure matters.

I only use ComfyUI on my own PC. Do I need to worry?

Your risk is low with default settings, because ComfyUI only listens on 127.0.0.1. Update anyway; it takes two minutes.

Which version is fixed?

The fix is commit 8a0f2fc412 on the main branch. No numbered release containing it was listed when I checked, so check for the commit with the git command above.

Has it been exploited in the wild?

The advisory does not report active attacks, and it is not on CISA’s Known Exploited Vulnerabilities list. Public details now make it easy to copy, so assume scanners will look for it.

Does the fix break my workflows?

It should not. It tightens how preview images, model notes and metadata are saved. Restart and refresh after updating.

Should I stop using Easy-Use?

Not necessarily. Popular packs get more scrutiny, which is how this was found. Keep it updated and keep ComfyUI off open networks.

Sources

Free weekly email

Get new AI guides every week

One short weekly email with our newest local AI, ComfyUI and AI tool guides. No spam, no pop-ups, just the good stuff.

Free. Unsubscribe anytime in one click. We only use your email to send this newsletter. See our privacy policy.

Woman in a home office holding a card reading EASY-USE, hook patch this ComfyUI node now