Flowise ist anfällig für das Schreiben beliebiger Dateien über sein WriteFileTool

The core of the vulnerability lies within the WriteFileTool component of Flowise, designed to handle large model files. Due to insufficient file path restrictions, an authenticated attacker can manipulate this tool to write files to any location on the server's file system. This is a significant risk because an attacker could overwrite critical system files, inject malicious code, or gain persistent access to the system. Successful exploitation could lead to complete system compromise, data exfiltration, and denial of service. The potential for remote command execution elevates the severity to critical, as it bypasses typical access controls.

Organizations deploying Flowise in production environments, particularly those using it to manage large AI models, are at significant risk. Shared hosting environments where multiple users share the same server are also vulnerable, as an attacker could potentially exploit the vulnerability through another user's Flowise instance. Legacy configurations with weak access controls exacerbate the risk.

• nodejs / server: Monitor process execution for unusual file write activity. Use lsof or fuser to identify processes accessing sensitive files.

lsof /etc/passwd

• nodejs / server: Examine Flowise application logs for requests related to the WriteFileTool, specifically looking for unusual file paths.

grep 'WriteFileTool' /var/log/flowise/app.log

• generic web: Check server access logs for requests containing suspicious file paths or attempts to access restricted directories.

1. 2025-10-09Disclosure

   disclosure

1. Reserviert2025-10-03
2. Veröffentlicht2025-10-09
3. Geändert2026-02-04
4. EPSS aktualisiert2026-03-23

The primary mitigation is to immediately upgrade Flowise to version 3.0.8 or later, which includes the necessary fix. If upgrading is not immediately feasible, consider implementing temporary workarounds. Restrict access to the WriteFileTool component to only trusted users and processes. Implement strict file system permissions to limit the attacker's ability to write to sensitive directories. Consider using a Web Application Firewall (WAF) to filter requests containing potentially malicious file paths. Regularly monitor system logs for suspicious file access activity.