CVE-2026-56672: ComfyUI: Stored XSS via /userdata/{file} due to Missing Content-Type Sanitization
ComfyUI is a node-based diffusion model GUI, API, and backend. Prior to 0.28.0, GET /userdata/{file} served user-controlled HTML and SVG files with extension-derived content types, allowing stored cross-site scripting in the ComfyUI origin and access to browser-stored API tokens, settings, workflows, and authenticated-equivalent API calls. The handler used web.FileResponse(path), so an uploaded .html/.svg was served as text/html/image/svg+xml. POST /userdata stores arbitrary request bodies (confined to the user's userdata directory). When a victim navigated to the file URL, the embedded script executed same-origin. The /view endpoint already forced dangerous MIME types to download; that protection had never been applied to /userdata. This issue is fixed in version 0.28.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ComfyUIto a version that resolves this vulnerability.Fixed in 0.28.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-56672?
The severity of CVE-2026-56672 is rated as high with a CVSS score of 8.2.
How do I fix CVE-2026-56672?
To fix CVE-2026-56672, upgrade to ComfyUI version 0.28.0 or later.
What type of vulnerability is CVE-2026-56672?
CVE-2026-56672 is a Stored Cross-Site Scripting (XSS) vulnerability.
What impact does CVE-2026-56672 have on users?
CVE-2026-56672 can lead to access of browser-stored API tokens and user settings due to the execution of malicious scripts.
Which versions of ComfyUI are affected by CVE-2026-56672?
Versions of ComfyUI prior to 0.28.0 are affected by CVE-2026-56672.