Le problème découle d'une validation manquante du champ pip dans une requête POST envoyée à l'endpoint /customnode/install utilisé pour installer des nœuds personnalisés qui est ajouté au serveur par l'extension. Ceci est une

The impact of CVE-2024-21574 is severe. An attacker who successfully exploits this vulnerability can achieve complete control over the ComfyUI-Manager server. This includes the ability to execute arbitrary commands, install malware, steal sensitive data, and potentially pivot to other systems on the network. The vulnerability's reliance on the pip package installer makes it particularly dangerous, as attackers can leverage malicious packages from compromised repositories or even host their own. Given ComfyUI-Manager's use in AI workflows, this could lead to data poisoning or the execution of unauthorized AI models, further expanding the potential damage. The lack of input validation directly enables this RCE, making it a high-priority concern.

Organizations and individuals utilizing ComfyUI-Manager for AI workflows, particularly those with exposed instances or those allowing custom node installations from untrusted sources, are at significant risk. Shared hosting environments where multiple users share the same ComfyUI-Manager instance are especially vulnerable, as an attacker could potentially compromise the entire environment through a single user's custom node installation.

• linux / server:

journalctl -u comfyui-manager -g 'pip install' | grep -i error

• python / supply-chain:

import subprocess
result = subprocess.run(['pip', 'install', '--version'], capture_output=True, text=True)
print(result.stdout)

• generic web:

curl -I http://<comfyui_manager_ip>/customnode/install | grep 'pip'

1. 2024-12-12Disclosure

   disclosure

1. Réservé2023-12-22
2. Publiée2024-12-12
3. EPSS mis à jour2026-04-02

The primary mitigation for CVE-2024-21574 is to immediately upgrade ComfyUI-Manager to version 2.51.1 or later. If upgrading is not immediately feasible due to compatibility concerns or breaking changes, consider implementing temporary workarounds. Restrict network access to the /customnode/install endpoint to trusted sources only. Implement a Web Application Firewall (WAF) with rules to block requests containing suspicious or malicious pip commands. Carefully review and validate any custom node installations before applying them. Monitor system logs for unusual pip activity or unexpected process executions. While a direct detection signature is difficult without deeper analysis of the pip install process, monitor for the execution of unusual Python scripts or the installation of unexpected packages.