Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
comfyui-easyuse-cve-check — Claude Code skill:唯讀檢查電腦上的 ComfyUI 是否受 CVE-2026-123790(Easy-Use 路徑穿越 → RCE)影響,含版本、修補 commit、--listen 對外開放與入侵跡象 | Kitploit
Tools/GitHubGitHub/lng255639-cpu/comfyui-easyuse-cve-check
Defensive ToolsVulnerability ScannersVulnerability AnalysisConfiguration AuditingWeb SecurityMisconfigurationIncident Response
GitHublng255639-cpu/comfyui-easyuse-cve-check

comfyui-easyuse-cve-check

Claude Code skill:唯讀檢查電腦上的 ComfyUI 是否受 CVE-2026-123790(Easy-Use 路徑穿越 → RCE)影響,含版本、修補 commit、--listen 對外開放與入侵跡象

View Repository
5 days agoNot yet reviewed
Share

comfyui-easyuse-cve-check

This Claude Code skill checks whether the ComfyUI on your computer is affected by CVE-2026-123790 (CERT/CC VU#944667). The vulnerability is in the ComfyUI-Easy-Use node: an attacker does not need to log in; as long as they can reach ComfyUI, they can overwrite the __init__.py of other nodes, and the attacker's code will be executed the next time ComfyUI restarts.

It checks:

  1. All ComfyUI installations on this computer, including the portable version, manual installations, and the Desktop version
  2. Whether the Easy-Use node is installed (including disabled ones), its version, and whether it includes the patch commit 8a0f2fc
  3. Whether ComfyUI is exposed to the LAN or the internet using --listen
  4. Whether there are signs of compromise: a node's __init__.py has been modified, or .py files have appeared in the input folder

Check only, no modifications. When a node needs to be removed or updated, Claude will ask you first before taking action.

English version: comfyui-easyuse-cve-check-en

Vulnerability Summary

ItemContent
IDCVE-2026-123790, CERT/CC VU#944667 (published 2026-11-12)
TypePath traversal (CWE-22), can lead to remote code execution
Affected versionsCERT/CC: below 1.4.1; other sources: 1.3.6–1.4.1
Attack entry pointPOST /easyuse/save/{name} (save_preview()), no login required
Fixcommit 8a0f2fc, only on the main branch, no official release greater than 1.4.1 yet
MitigationRemove this node, or only allow trusted people to connect to ComfyUI

By default, ComfyUI only listens on the local machine (127.0.0.1). Without --listen, other computers cannot connect, so the risk is much lower. However, as long as an affected version is installed, it is still recommended to remove or update it.

Installation

Requires Claude Code and Python 3.8 or later (standard library only). Checking the patch commit requires git; without git, only the version number will be used for the determination.

git clone https://github.com/lng255639-cpu/comfyui-easyuse-cve-check.git ~/.claude/skills/comfyui-easyuse-cve-check

On Windows, ~ is C:\Users\<your username>.

How to Use

Enter in Claude Code:

/comfyui-easyuse-cve-check

Or simply say "help me check whether ComfyUI is affected by the Easy-Use vulnerability".

Running the Script Yourself (Without Claude)

python ~/.claude/skills/comfyui-easyuse-cve-check/check_easyuse.py
ParameterPurpose
--path DIRSpecify a ComfyUI folder (or its parent folder); can be used multiple times
--only-pathOnly search the locations specified by --path
--depth NSearch depth, default 5
--out FILESave the results to a JSON file

By default, it searches the home directory, the basePath configured in ComfyUI Desktop, and every disk.

Values of summary.overall:

ValueMeaning
no_comfyui_foundNo ComfyUI found
not_affectedComfyUI exists, but no Easy-Use
patchedPatched
affected_local_onlyAffected, but only listening on the local machine
affected_exposedAffected and exposed to the LAN or the internet; take action immediately

Limitations

  • If the node was not installed via git clone (for example, downloaded as a zip and extracted), there is no way to confirm whether the patch commit is present; only the version number can be checked. If the version cannot be read, it will be treated as affected.
  • The compromise check can only compare nodes managed by git; nodes without .git will be listed but cannot be compared.
  • The listening status only reflects the situation at the moment the check is run; when ComfyUI is not running, the startup script is examined instead.
  • It is not possible to test from the internet whether the router forwards the port; you need to check this yourself on the router.

Files

comfyui-easyuse-cve-check/
├── SKILL.md           ← the workflow Claude reads
├── README.md          ← this description
└── check_easyuse.py   ← read-only check script
Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    867
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    544
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    385
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    360
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    302
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    279

Explore all tools

Browse our collection of tools

View all tools →