Is there a public PoC exploit available for CVE-2026-6589?

Yes, a public proof-of-concept exploit is available for CVE-2026-6589. Prioritise patching immediately. EPSS: 0.0%.

Comfyui CVE-2026-6589

Q: What is the CVSS score of CVE-2026-6589?

CVE-2026-6589 has a CVSS 4.0 base score of 2.1 (Low). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-23731 LOW

Cross-Site Request Forgery (CSRF) (CWE-352)

2026-04-20 VulDB

CSRF Comfyui

2.1

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

2.1 LOW

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Scope

Lifecycle Timeline

Severity Changed

Apr 29, 2026 - 01:12 NVD

MEDIUM LOW

CVSS changed

Apr 29, 2026 - 01:12 NVD

5.3 (MEDIUM) 2.1 (LOW)

PoC Detected

Apr 29, 2026 - 01:00 vuln.today

Public exploit code

CVSS changed

Apr 20, 2026 - 01:22 NVD

4.3 (MEDIUM) 5.3 (MEDIUM)

Analysis Generated

Apr 20, 2026 - 01:18 vuln.today

EUVD ID Assigned

Apr 20, 2026 - 01:15 euvd

EUVD-2026-23731

Analysis Generated

Apr 20, 2026 - 01:15 vuln.today

CVE Published

Apr 20, 2026 - 00:30 nvd

LOW 2.1

DescriptionCVE.org

A security vulnerability has been detected in ComfyUI up to 0.13.0. This affects the function create_origin_only_middleware of the file server.py. The manipulation leads to cross-site request forgery. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

AnalysisAI

Cross-site request forgery (CSRF) in ComfyUI up to version 0.13.0 allows unauthenticated remote attackers to modify application state via crafted requests to the create_origin_only_middleware function in server.py. The vulnerability requires user interaction (clicking a malicious link or visiting an attacker-controlled site) but has low integrity impact and is publicly exploitable with proof-of-concept code available. The vendor has not responded to early disclosure notification.

Technical ContextAI

ComfyUI is a node-based UI for Stable Diffusion and other generative AI models. The vulnerability resides in the create_origin_only_middleware function within server.py, which is responsible for managing cross-origin request policies. The root cause is classified under CWE-352 (Cross-Site Request Forgery), indicating insufficient CSRF token validation or origin verification when processing state-modifying requests. The CVSS vector AV:N/AC:L/PR:N/UI:R indicates the flaw is exploitable over the network without authentication but requires user interaction (UI:R), such as clicking a malicious link while authenticated to ComfyUI. The affected CPE encompasses all versions of ComfyUI up to and including 0.13.0.

RemediationAI

Upgrade ComfyUI to a version released after the disclosure; however, no specific patched version number is confirmed in available data due to lack of vendor response. Until an official patch is available, apply these compensating controls: (1) Implement strict Content Security Policy (CSP) headers restricting frame-ancestors and preventing cross-site framing, which mitigates CSRF by reducing the attack surface; (2) Configure SameSite=Strict cookies for all session tokens to prevent cookie transmission in cross-site requests, though this may affect legitimate cross-domain workflows; (3) Restrict ComfyUI access to authenticated users only and use a WAF or reverse proxy to enforce origin whitelisting, explicitly rejecting requests from untrusted origins; (4) Deploy ComfyUI behind a CSRF token validation layer (e.g., nginx module or reverse proxy middleware) that enforces token verification on all state-modifying requests (POST/PUT/DELETE). Monitor the VulDB advisory and ComfyUI GitHub repository for patch announcements. Contact the ComfyUI maintainers directly via GitHub issues if patch status remains unclear.