Quick answers
- Is CVE-2026-56672 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56672 being exploited in the wild.
- How severe is CVE-2026-56672?
- High severity, with a CVSS score of 8.2, published 31 July 2026.
- Which products and versions are affected?
- Comfy-Org ComfyUI < 0.28.0.
- Is there a fix for CVE-2026-56672?
- A patch was published on 2026-07-02: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-56672 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-56672?
- Check whether you run Comfy-Org ComfyUI at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A stored cross-site scripting (XSS) vulnerability exists in ComfyUI prior to version 0.28.0. The 'GET /userdata/{file}' endpoint served user-uploaded files using extension-derived Content-Types without proper sanitization or download enforcement. An attacker can use 'POST /userdata' to upload malicious HTML or SVG files containing scripts. When a victim navigates to the file's URL, the script executes within the ComfyUI origin, providing access to browser-stored API tokens (auth_token_comfy_org), settings, and workflows. The fix in version 0.28.0 forces dangerous MIME types to 'application/octet-stream' and implements 'Content-Disposition: attachment' and 'X-Content-Type-Options: nosniff'.
Affected products
- Comfy-Org ComfyUI < 0.28.0
Timeline
- 2026-07-02: patched: Fix committed to repository
- 2026-07-15: advisory: GitHub Security Advisory published
- 2026-07-31: disclosed: CVE published to NVD