Quick answers
- Is CVE-2026-56670 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56670 being exploited in the wild.
- How severe is CVE-2026-56670?
- 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-56670?
- 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-56670 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-56670?
- 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's /view endpoint. The root cause is the omission of 'image/svg+xml' and related XML content types from the application's dangerous-content-type blocklist. An unauthenticated attacker can upload a malicious SVG file containing inline scripts (e.g., via the /upload/image endpoint). When a user views this file, the server renders it inline without a 'Content-Disposition: attachment' header, leading to script execution within the ComfyUI origin. This allows for the exfiltration of API tokens and browser-stored data. The issue is resolved in version 0.28.0 by forcing a download (application/octet-stream) for these content types.
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