ComfyUI-Easy-Use Flaw Plants Code in Custom Nodes for the Next Restart
An exposed save-preview route can replace a custom node’s Python entry point. Remove the extension or limit ComfyUI access while checking node files for replacement.

A ComfyUI server with the Easy-Use extension can let someone who reaches its exposed routes replace a custom node’s Python entry point without logging in. CERT/CC’s November 12 vulnerability note says the replacement runs as the ComfyUI process when the server restarts. For teams running ComfyUI to build AI workflows, the restart is the point where a file change becomes code execution.
CERT/CC identifies ComfyUI-Easy-Use 1.4.1 and earlier as affected. Its note says Nguyen Huy Hoang reported the issue, now tracked as CVE-2026-123790. An attacker needs network access to the affected routes without authentication; the issue requires no user interaction.
Preview save overwrites custom-node entry points
Easy-Use adds custom nodes and workflow utilities to ComfyUI. The CVE Program record, assigned by CERT/CC, identifies the affected handler as save_preview() on POST /easyuse/save/{name}. It says the handler checks the source directory before appending a user-supplied filename, then permits the custom_nodes directory as a copy destination. CERT/CC describes the resulting file movement: an uploaded Python file in ComfyUI’s input directory can replace an installed custom node’s __init__.py.
“Upon restart, ComfyUI will import and execute the modified node,” CERT/CC writes. The replacement can sit on disk until ComfyUI imports the node at restart. After restart, the code inherits the ComfyUI process’s privileges. CERT/CC says that access could reach models, workflows, other readable files and credentials available in the process environment. The CVE record explicitly lists versions 1.3.6 through 1.4.1; use CERT/CC’s broader “1.4.1 and earlier” language when identifying installations to investigate.
Remove Easy-Use or limit who reaches ComfyUI
For an instance whose Easy-Use routes are reachable by untrusted users, remove the extension or put ComfyUI behind access restricted to trusted users, as CERT/CC recommends. Inventory the installed Easy-Use version and the actual network path to the server. A host that is reachable only through an authenticated gateway has a different exposure path from one whose affected route is directly reachable without authentication.
CERT/CC identifies a fix on the project’s main branch at commit 8a0f2fc412. Verify that the installed extension contains that change before treating an upgrade as remediation. CERT/CC says it could not reach the maintainer during coordination; its vendor table lists the response status as unknown.
Compare node files before the next restart
Inspect installed custom nodes’ __init__.py files for unexpected changes, using a trusted copy of each node to compare content or hashes; check the ComfyUI input directory for unfamiliar uploaded Python files. If the service records HTTP access, review requests to the Easy-Use save route alongside file modification times. Compare those clues with trusted node-file hashes to decide whether a node changed. Where a node entry point has been replaced, isolate the instance, restore trusted node files and assess credentials available to the ComfyUI process before restarting it again.
Confirm the chosen control at the actual route: access should be limited to trusted users, the extension should be absent, or the installed code should include the identified fix. A quiet process between restarts is a weak signal here; the file on disk and the access path tell you whether the described route still poses a problem.