Is it safe to run ComfyUI with --listen, and what security controls does ComfyUI (v0.42.1) and ComfyUI-Manager (4.3) document?
At ComfyUI tag v0.42.1 (2026-10-19): the server binds 127.0.0.1:8188 by default; --listen with no value binds 0.0.0.0 and ::. SECURITY.md defines the threat model as local-only: anyone who can reach the URL is trusted, custom nodes are arbitrary trusted Python, and issues requiring --listen or other network exposure are treated as bugs, not vulnerabilities; securing an exposed server (firewall, reverse proxy, authentication) is the user's responsibility. cli_args.py offers TLS (--tls-keyfile/--tls-certfile), --enable-cors-header (default "*" when given without a value), --multi-user (per-user storage, not authentication), --disable-all-custom-nodes with --whitelist-custom-nodes, and --offline (restrictive CSP, disables partner nodes); no login/auth flag exists in that file. ComfyUI-Manager 4.3 config.ini: security_level strong|normal|normal-|weak and network_mode public|private|offline|personal_cloud; on non-local listeners high-risk features are blocked unless weak or personal_clou...
Structured fields
{
"citations": [
{
"url": "https://raw.githubusercontent.com/Comfy-Org/ComfyUI/63be2f9b82ad0dac88a7ceaa28a9cf3154125a18/SECURITY.md",
"note": "## Scope para 1; ## What We Do Not Consider... bullet 1; line 63; grep auth|password (0 hits); lines 216-228, 320-361"
},
{
"url": "https://raw.githubusercontent.com/Comfy-Org/ComfyUI/63be2f9b82ad0dac88a7ceaa28a9cf3154125a18/comfy/cli_args.py",
"note": "## Scope para 1; ## What We Do Not Consider... bullet 1; line 63; grep auth|password (0 hits); lines 216-228, 320-361"
},
{
"url": "https://raw.githubusercontent.com/Comfy-Org/ComfyUI-Manager/f764cc0e54ca8cd6e1c6a8ecc005bd574592ca65/README.md",
"note": "## Scope para 1; ## What We Do Not Consider... bullet 1; line 63; grep auth|password (0 hits); lines 216-228, 320-361"
}
]
}Evidence claims
- [sourced_fact] At ComfyUI tag v0.42.1 (2026-10-19): the server binds 127.0.0.1:8188 by default; --listen with no value binds 0.0.0.0 and ::. SECURITY.md defines the threat model as local-only: anyone who can reach the URL is trusted, custom nodes are arbitrary trusted Python, and issues requiring --listen or other network exposure are treated as bugs, not vulnerabilities; securing an exposed server (firewall, reverse proxy, authentication) is the user's responsibility. cli_args.py offers TLS (--tls-keyfile/--tls-certfile), --enable-cors-header (default "*" when given without a value), --multi-user (per-user storage, not authentication), --disable-all-custom-nodes with --whitelist-custom-nodes, and --offline (restrictive CSP, disables partner nodes); no login/auth flag exists in that file. ComfyUI-Manager 4.3 config.ini: security_level strong|normal|normal-|weak and network_mode public|private|offline|personal_cloud; on non-local listeners high-risk features are blocked unless weak or personal_cloud; git-URL and pip installs are now separate opt-in flags (allow_git_url_install, allow_pip_install) still denied on non-local listeners unless personal_cloud. Practical rule: never expose ComfyUI directly; put it behind an authenticating reverse proxy/VPN, keep Manager at normal or strong, and treat every custom node as code you run. · locator: ## Scope para 1; ## What We Do Not Consider... bullet 1; line 63; grep auth|password (0 hits); lines 216-228, 320-361 source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |
Linked records
- cites → https://raw.githubusercontent.com/Comfy-Org/ComfyUI-Manager/f764cc0e54ca8cd6e1c6a8ecc005bd574592ca65/README.md
- cites → https://raw.githubusercontent.com/Comfy-Org/ComfyUI/63be2f9b82ad0dac88a7ceaa28a9cf3154125a18/SECURITY.md
- cites → https://raw.githubusercontent.com/Comfy-Org/ComfyUI/63be2f9b82ad0dac88a7ceaa28a9cf3154125a18/comfy/cli_args.py