Skip to main content

Comfyui EUVDEUVD-2026-23737

| CVE-2026-6592 LOW
Cross-site Scripting (XSS) (CWE-79)
2026-04-20 VulDB
2.0
CVSS 4.0 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to ComfyUI
  2. Delivery
    Submit XSS payload via userdata endpoint
  3. Exploit
    Payload stored in user data
  4. Execution
    Victim views attacker's profile
  5. Persist
    Malicious script executes in victim's browser
  6. Impact
    Attacker harvests session token or credentials

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires: (1) Valid authentication to the ComfyUI instance (PR:L); (2) Ability to submit data to the getuserdata endpoint or user profile modification endpoint (no special configuration needed for standard deployments); (3) Another user must view the attacker's injected data or click a link containing the malicious payload (UI:R). The vulnerability is NOT exploitable against default configurations without a login credential. Exploitation is limited to the user's current security context (S:U) - XSS payload cannot escalate privileges or access other users' data directly but can steal session cookies or perform actions as the victim.

Impact

CVSS 3.5 (Low) with EPSS data unavailable suggests limited real-world risk despite public exploit availability. The Low CVSS reflects mandatory constraints: PR:L (login required), UI:R (user interaction required), and S:U (scope unchanged-impact limited to same security context). CVSS vector shows AC:L (low complexity) and AV:N (network-accessible), making exploitation straightforward once authenticated, but the authentication and interaction barriers significantly reduce attack surface. Public exploit availability (POC confirmed) increases concern for targeted attacks against ComfyUI instances, but absence from CISA KEV indicates no confirmed active exploitation in the wild at analysis time. Risk is elevated in multi-user ComfyUI deployments where an attacker with login access could inject payloads affecting other users, particularly if the instance is exposed to untrusted networks. For single-user local installations, risk is minimal. E:P (exploit code mature/proof-of-concept exists) and RL:X (vendor has not issued a patch) compound the remediation burden.

Exploit ScenarioDerived

An authenticated attacker logs into a ComfyUI instance and injects malicious JavaScript into a user profile field (e.g., username, email, or preferences) via the userdata endpoint. When another user or an administrator views the attacker's profile or user list, the injected script executes in their browser with their session privileges, allowing session hijacking, credential theft, or further system compromise. The publicly available exploit (gist.github.com/YLChen-007/50f0cdc5e3f7b737ce99c783e487ca0d) provides proof-of-concept payloads.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 20, 2026

Stored cross-site scripting (XSS) in ComfyUI's userdata endpoint (getuserdata function in app/user_manager.py) allows authenticated attackers to inject malicious scripts that execute in other users' browsers. Affected versions range from 0.1 through 0.13.0. The vulnerability requires user interaction (UI:R) and authenticated access (PR:L), limiting real-world impact, but publicly available exploit code exists and the vendor has not responded to disclosure.

RemediationAI

No vendor-released patch identified at time of analysis - the vendor was contacted early but did not respond. Immediate remediation options include: (1) Upgrade to a patched version if available (verify with upstream project or official release channels for versions after 0.13.0); (2) Apply input validation and output encoding to the getuserdata function in app/user_manager.py - specifically, HTML-encode or sanitize all user-controlled data before inclusion in responses; (3) Implement Content Security Policy (CSP) headers with script-src 'self' to restrict inline script execution; (4) Restrict userdata endpoint access via network segmentation or authentication gateway if ComfyUI is exposed to untrusted networks; (5) For high-risk deployments, disable the userdata endpoint or user profile features if operationally feasible. Monitor upstream ComfyUI repository and issue trackers for security patches. Refer to VulDB (vuldb.com/vuln/358227) for updates.

Affected VersionsENISA

comfyui 0.7
comfyui 0.8
comfyui 0.2
comfyui 0.11
comfyui 0.13.0
comfyui 0.10
comfyui 0.12
comfyui 0.9
comfyui 0.3
comfyui 0.1
comfyui 0.6
comfyui 0.4
comfyui 0.5

Affected Packages

euvd comfyui no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

ComfyUI is a node-based UI for Stable Diffusion that manages user data via a REST endpoint. The userdata endpoint's getuserdata function fails to sanitize user-supplied input before reflecting it in HTTP responses, creating a stored XSS vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation). The attack surface is the app/user_manager.py component, specifically the endpoint handling user profile or preference data. Because the CVSS vector specifies PR:L (requires login) and UI:R (requires user interaction to trigger the payload), exploitation is limited to authenticated users and requires a victim to view the malicious data in their own session or click a crafted link.

Know when Comfyui gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 2.0 LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
Passive
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

6
Severity Changed
Apr 29, 2026 - 01:12 NVD
MEDIUM LOW
CVSS changed
Apr 29, 2026 - 01:12 NVD
5.1 (MEDIUM) 2.0 (LOW)
PoC Detected
Apr 29, 2026 - 01:00 vuln.today
Public exploit code
Severity Changed
Apr 20, 2026 - 02:22 NVD
LOW MEDIUM
CVSS changed
Apr 20, 2026 - 02:22 NVD
3.5 (LOW) 5.1 (MEDIUM)
CVE Published
Apr 20, 2026 - 01:15 nvd
LOW 2.0

DescriptionCVE.org

A vulnerability has been found in ComfyUI up to 0.13.0. Affected by this vulnerability is the function getuserdata of the file app/user_manager.py of the component userdata Endpoint. Such manipulation leads to cross site scripting. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Threat Intelligence Overview

EPSS Score
0.0%
Top 92% exploitable
Exploit
POC
Public exploit code exists
Social Media
1
Sightings
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy