Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Unauthenticated network POST /prompt with no user interaction and low complexity yields confidentiality-only file disclosure; no integrity or availability impact, so I:N/A:N.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
4DescriptionCVE.org
ComfyUI is a modular diffusion model GUI, API, and backend with a graph-and-node interface. Prior to 0.28.0, folder_paths.get_annotated_filepath and exists_annotated_filepath join workflow-controlled annotated filenames to a base directory without a containment check, allowing an unauthenticated crafted POST /prompt workflow using LoadImage or sibling nodes to probe arbitrary host paths and exfiltrate image-format files through /view. LoadImage defines a VALIDATE_INPUTS method, which causes the execution engine to skip COMBO (input-directory) validation. Affected nodes include LoadImage, LoadImageMask, LoadImageOutput, LoadAudio, LoadLatent, LoadVideo, and Load3D. This issue is fixed in version 0.28.0.
AnalysisAI
Path traversal arbitrary file read in ComfyUI (comfy-org) before 0.28.0 lets remote unauthenticated attackers probe arbitrary host filesystem paths and exfiltrate image-format files via the /view endpoint. A crafted POST /prompt workflow using LoadImage or sibling loader nodes joins attacker-controlled annotated filenames to a base directory with no containment check, and LoadImage's VALIDATE_INPUTS method causes the engine to skip input-directory validation. Rated CVSS 7.5 (confidentiality-only); no public exploit identified at time of analysis and it is not on CISA KEV.
Technical ContextAI
ComfyUI is a modular node/graph GUI and API backend for diffusion (Stable Diffusion) image generation, exposing an HTTP API where workflows are submitted as JSON. The root cause is CWE-22 (Improper Limitation of a Pathname to a Restricted Directory / path traversal): folder_paths.get_annotated_filepath and exists_annotated_filepath build a filesystem path by joining a workflow-supplied 'annotated' filename (which encodes a base directory such as input/output/temp) to a base directory without verifying the result stays inside that directory, so sequences like ../../ escape it. Compounding this, the LoadImage node declares a VALIDATE_INPUTS method, which signals the execution engine to bypass the normal COMBO validation that would otherwise restrict the value to entries actually present in the input directory. The fix in PR #14734 introduces a reusable folder_paths.is_within_directory() containment helper that realpaths both the base directory and target (also defeating symlink escape) and requires commonpath to equal the base directory; the same PR hardens the model-preview and userdata endpoints and adds is_dangerous_content_type() to force risky MIME types to download.
RemediationAI
Vendor-released patch: upgrade to ComfyUI 0.28.0 or later, which adds the folder_paths.is_within_directory() containment check per advisory GHSA-rvxv-29p8-pxgq (https://github.com/Comfy-Org/ComfyUI/security/advisories/GHSA-rvxv-29p8-pxgq) and PR #14734 (https://github.com/Comfy-Org/ComfyUI/pull/14734). If you cannot upgrade immediately, do not expose the ComfyUI API to untrusted networks: bind it to localhost or place it behind a reverse proxy or VPN that enforces authentication, and restrict or block unauthenticated access to the POST /prompt and GET /view endpoints, since these are the ingestion and exfiltration paths - the trade-off is that remote and multi-user workflow submission will be blocked. Run the ComfyUI process under a low-privilege account with a restricted filesystem view (for example a container or chroot) so that traversal reads reach as few sensitive files as possible, accepting the operational overhead of containerization. Avoid loading untrusted workflow JSON from third parties until patched.
Arbitrary file write via path traversal in ComfyUI before 0.30.0 lets an attacker place attacker-controlled content anyw
comfyanonymous/comfyui version v0.2.4 suffers from a non-blind Server-Side Request Forgery (SSRF) vulnerability. Rated h
A stored cross-site scripting (XSS) vulnerability exists in comfyanonymous/comfyui version 0.2.2 and possibly earlier. R
Remote code execution in ComfyUI v0.23.0 (and all prior 0.x releases) lets unauthenticated attackers run arbitrary Pytho
Stored cross-site scripting in ComfyUI (Comfy-Org) before 0.28.0 lets an attacker upload HTML or SVG to the per-user use
Stored cross-site scripting in ComfyUI before 0.28.0 lets an attacker upload a malicious SVG that the /view endpoint ser
Unauthenticated information disclosure in ComfyUI (comfy-org/comfyui) before 0.28.0 lets remote attackers read arbitrary
Path traversal in ComfyUI up to version 0.13.0 allows authenticated remote attackers to read arbitrary files on the serv
Path traversal in ComfyUI up to version 0.13.0 allows authenticated remote attackers to read arbitrary files via manipul
Cross-site request forgery (CSRF) in ComfyUI up to version 0.13.0 allows unauthenticated remote attackers to modify appl
Cross-site scripting (XSS) in ComfyUI up to version 0.13.0 allows authenticated remote attackers to inject malicious scr
Stored cross-site scripting (XSS) in ComfyUI's userdata endpoint (getuserdata function in app/user_manager.py) allows au
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-51403