Comfyui CVE-2026-6589

User must have an active authenticated session with ComfyUI at the time the CSRF payload is delivered. The ComfyUI server must be accessible over the network (local, private network, or public internet). The user must visit an attacker-controlled webpage or click a malicious link while authenticated to ComfyUI in the same browser or browser tab. The create_origin_only_middleware function must fail to properly validate request origin via CSRF token or strict origin checking. The vulnerability is NOT exploitable against ComfyUI instances with properly configured same-site cookies, strict CSP policies, or correct CSRF token validation. Exploitation is limited to low-integrity modifications; attackers cannot read sensitive data (no confidentiality impact) or cause denial of service (no availability impact).

This vulnerability presents moderate real-world risk with several mitigating factors. The CVSS score of 4.3 and CVSS:3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N indicate network-accessible exploitation without authentication but with mandatory user interaction and limited integrity impact (I:L). The EPSS probability is not provided, limiting quantitative risk estimation. The E:P (Exploit Code Mature) field confirms publicly available POC code, and the RL:X (Unknown Release) suggests no vendor patch timeline has been communicated. The vulnerability requires user interaction (UI:R), which significantly reduces real-world exploitation probability compared to fully automated attacks; an attacker must trick a user into visiting a malicious site or clicking a link while the victim has ComfyUI open. The integrity impact is classified as Low (I:L), meaning attackers can only make limited modifications to application data rather than achieving complete compromise. The lack of vendor response raises concerns about patch availability and security posture, but the UI requirement and low integrity impact suggest this is not a critical priority compared to pre-authentication remote code execution flaws. Organizations using ComfyUI in multi-user or internet-facing deployments should prioritize patching once available; isolated or development-only instances face lower risk.

An attacker crafts a malicious webpage or email containing a hidden form or script that targets the ComfyUI server running on a victim's local network or public instance. When a user with an active ComfyUI session visits the attacker's page, the embedded request (e.g., an image tag, fetch request, or form submission) exploits the CSRF vulnerability in create_origin_only_middleware to perform unauthorized actions such as modifying model settings, altering workflow parameters, or injecting malicious nodes into the user's session. The user may not notice the attack if the integrity impact is subtle (e.g., a workflow parameter change that goes undetected until workflow execution).