comfyanonymous comfyui utils.py set_attr 动态确定的对象属性

The vulnerability lies in the set_attr function, which allows for the dynamic setting of object attributes. An attacker could leverage this to modify the behavior of ComfyUI, potentially leading to arbitrary code execution or denial of service. While the complexity of the attack is considered high, the public disclosure of the exploit increases the risk of exploitation. The ability to launch the attack remotely expands the potential attack surface, making systems running vulnerable versions of ComfyUI susceptible to compromise.

Users running ComfyUI version 0.3.40 are at direct risk. This includes individuals and organizations utilizing ComfyUI for AI image generation and experimentation. Shared hosting environments where ComfyUI is deployed could also be affected, potentially impacting multiple users.

• python / ComfyUI:

import os
import subprocess

# Check ComfyUI version
process = subprocess.Popen(['comfyui', '--version'], stdout=subprocess.PIPE, stderr=subprocess.PIPE)
stdout, stderr = process.communicate()
version = stdout.decode('utf-8').strip()

if version == '0.3.40':
    print('Vulnerable ComfyUI version detected!')
else:
    print('ComfyUI version is not vulnerable.')

• python / ComfyUI: Monitor file system for modifications to /comfy/utils.py

import os
import time

file_path = '/comfy/utils.py'

while True:
    try:
        last_modified = os.path.getmtime(file_path)
        time.sleep(60)  # Check every minute
        current_modified = os.path.getmtime(file_path)
        if current_modified != last_modified:
            print(f'File {file_path} has been modified!')
            break
    except FileNotFoundError:
        print(f'File {file_path} not found.')
        break

1. 2025-06-16Disclosure

   disclosure

2. 2025-06-16Patch

   patch

1. 已保留2025-06-15
2. 发布日期2025-06-16
3. 修改日期2025-06-23
4. EPSS 更新日期2026-03-23

The primary mitigation is to upgrade ComfyUI to version 0.3.41 or later, which contains the fix for this vulnerability. If upgrading is not immediately feasible, consider implementing input validation on the attributes being set within the setattr function to restrict the values that can be assigned. While a direct WAF rule is unlikely, monitoring network traffic for unusual requests targeting /comfy/utils.py could provide early warning signs of exploitation attempts. After upgrading, confirm the fix by attempting to trigger the vulnerable setattr function with malicious input and verifying that it is properly handled.