CVE-2026-68771 Comfy-Org CVE debrief

Who should care

Users of ComfyUI v0.23.0, administrators of systems where ComfyUI is deployed, security teams responsible for monitoring and patching vulnerabilities, and operators managing affected platforms should prioritize patching due to the critical vulnerability allowing unauthenticated remote code execution. Compensating controls and monitoring should be reviewed for exposed systems while remediation is scheduled and verified. Asset inventory and vulnerability management processes should be updated to reflect this critical vulnerability. Security teams should track exceptions, retest remediated assets, and close the item only after evidence is documented. Affected product deployments should be confirmed in managed environments, and owners should be assigned for follow-up. Official advisories or CVE records should be reviewed to validate affected scope, severity, and vendor guidance. Change control processes should be used for vendor-supported updates or mitigations where exposure is confirmed. Monitoring, detection, and logs should be checked for exposed assets that need extra review. The vulnerability's impact on operational security and potential business disruption should be assessed. Communication plans should be developed for stakeholders in case of an incident. Compliance and regulatory requirements related to vulnerability management should be reviewed and addressed. Incident response plans should be updated to include scenarios involving exploitation of this vulnerability. Training or awareness programs for security and IT staff should be considered to improve response to similar vulnerabilities in the future. The vulnerability's potential impact on third-party services or dependencies should be evaluated. Business continuity plans should be reviewed in light of potential disruptions caused by exploitation of this vulnerability. The effectiveness of current security controls in preventing exploitation should be assessed. The vulnerability's potential impact on customer data and privacy should be evaluated. The vulnerability's potential impact on organizational reputation and brand should be considered. The vulnerability's alignment with industry-specific threat,

Technical summary

ComfyUI v0.23.0 contains an unsafe deserialization vulnerability in the LoadTrainingDataset node. An attacker can exploit this by uploading a crafted pickle file via the unauthenticated POST /upload/image endpoint and then queuing a workflow graph via POST /prompt, triggering the deserialization of the malicious pickle payload. This allows for arbitrary Python code execution as the ComfyUI process user. The vulnerability has a CVSS score of 9.3, indicating critical severity.

Defensive priority

ComfyUI v0.23.0 users should prioritize patching due to a critical vulnerability allowing unauthenticated remote code execution.

Recommended defensive actions

• Apply patches or updates provided by the vendor to address the vulnerability
• Restrict access to the /upload/image and /prompt endpoints to authenticated users only
• Monitor for suspicious activity and implement compensating controls until a patch is available
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Review compensating controls for exposed systems while remediation is scheduled and verified

Evidence notes

ComfyUI v0.23.0 has an unsafe deserialization vulnerability in the LoadTrainingDataset node, allowing unauthenticated remote attackers to execute arbitrary Python code. Attackers can upload malicious pickle files via the POST /upload/image endpoint and trigger deserialization by queuing a workflow graph via POST /prompt. The vulnerability is critical, with a CVSS score of 9.3. Users should verify affected deployments, review official advisories, and plan for vendor-supported updates or mitigations. Evidence is limited to CVE details and NVD information.

Official resources