CVE-2026-56673 Comfy-Org CVE debrief

Who should care

Defenders responsible for ComfyUI deployments should assess exposure and prioritize patching to version 0.28.0 or later. They should also verify input validation for LoadImage and sibling nodes, and monitor for suspicious activity on /prompt workflows. Security teams and vulnerability management teams should review the issue and plan for remediation.

Why it matters

CVE-2026-56673 is a high-severity vulnerability in ComfyUI that allows unauthenticated attackers to probe host paths and exfiltrate files. Defenders should prioritize patching, verify input validation, and monitor for suspicious activity.

• Path traversal allows attackers to probe arbitrary host paths
• Exfiltration of image-format files is possible through /view
• Input validation for LoadImage and sibling nodes requires verification
• Patching to version 0.28.0 or later is required for fix

Technical summary

The vulnerability is caused by a lack of containment checks in folder_paths.get_annotated_filepath and exists_annotated_filepath, allowing attackers to access arbitrary host paths through crafted POST /prompt workflows using LoadImage or sibling nodes. LoadImage defines a VALIDATE_INPUTS method, which causes the execution engine to skip COMBO (input-directory) validation. This issue is fixed in version 0.28.0. Defenders should prioritize patching and verify input validation for LoadImage and sibling nodes, and monitor for suspicious activity.

Defensive priority

Defenders should prioritize patching to version 0.28.0 or later, verify input validation, and monitor for suspicious activity.

Recommended defensive actions

• Patch ComfyUI to version 0.28.0 or later
• Verify input validation for LoadImage and sibling nodes
• Monitor for suspicious activity on /prompt workflows
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by a lack of containment checks in folder_paths.get_annotated_filepath and exists_annotated_filepath, allowing attackers to access arbitrary host paths through crafted POST /prompt workflows using LoadImage or sibling nodes. The issue is fixed in version 0.28.0. Source confidence is limited to public statements and vendor advisories.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.