Requesting a manual review of **cglide** version **1.2.8**, which is `NodeVersionStatusFlagged`. id:26408852-3276-48dc-bfbb-aa00aea8ccde

The only Active version is 1.0.4, published 2026-08-24. Every version since is flagged, so Manager and registry search serve a build that predates all of this year's fixes to the pack, including the security remediation described below. That is the part I would most like resolved — users are currently getting the oldest code, not the newest.

API status

• Node: https://api.comfy.org/nodes/cglide
• Versions: https://api.comfy.org/nodes/cglide/versions
• Active/Pending: GET .../versions?statuses=NodeVersionStatusActive&statuses=NodeVersionStatusPending returns a single entry, 1.0.4, id f16a8df3-f0ff-4f38-8428-13bc1c579672, created 2026-08-24
• Version under review: 1.2.8, id <PASTE 1.2.8 id>
• Repository: https://github.com/CGlide/ComfyUI-CGlide
• Publisher: cglide

History, stated up front

Versions 1.0.5 through 1.2.3 were banned over several real issues — RCE, command injection, SSRF and path traversal. Those were fair calls and each one was fixed. The SSRF guard landed in 1.2.4: scheme allowlist, hostnames resolved and checked before the request, loopback/private/link-local blocked, redirects re-validated per hop, response size capped, LAN hosts opt-in by environment variable rather than taken from the request.

Nothing has been banned since. Versions 1.2.4 through 1.2.8 carry no policy-v0.x message and no reviewer in status_reason — only the raw scanner array.

What 1.2.8 is flagged on

Six findings, all "severity": "info" in the registry's own JSON.

3 × python_command_injection_risk — csglide_run.py lines 96, 116, 143. This is the pack's ffmpeg layer. In 1.2.7 I consolidated every subprocess call in the pack into this single module so there is one place to audit rather than eight call sites across four files. All three are list-form argv with shell=False, every argument is checked to be a str, and run()/popen() refuse any executable the module did not resolve itself — the raise is visible directly above each flagged line in the report's own snippet. Line 143 is the resolver probing a candidate with the literal -version.

2 × python_environment_manipulation — CSGLIDE_FFMPEG (lets a user point the pack at their own ffmpeg build) and CSGLIDE_VISION_ALLOW_HOSTS, which is the SSRF remediation itself.

1 × python_network_operations — $socket4 matching the substring .bind( in inspect.signature(executor.original).bind(*args, **kwargs). That file imports base64, inspect, io, math, torch, PIL and latent_preview; it has no network capability at all. Same pattern reported in #3206.

Ask

Please re-review 1.2.8 and, if it passes, clear the flag so there is an installable recent version.

If a specific pattern is the blocker rather than the whole set, I would like to know which, so later versions do not stay hidden from Manager for the same reason. The pack encodes video, so it will always call ffmpeg via subprocess; if that is disqualifying on its own I would rather be told plainly than keep publishing versions to find out.