An unauthenticated remote code execution vulnerability in Flowise allows attackers to achieve full system compromise via insecure configuration injection.

This vulnerability stems from an insecure implementation of the overrideConfig option, which lacks an allow-list for permitted variables and relies on an insufficient vm2 sandbox. Attackers can leverage this to execute arbitrary code, perform SSRF, or exfiltrate sensitive server-side data without prior authentication.

With a CVSS score of 9.8, this critical vulnerability poses a severe risk of total server compromise. Successful exploitation allows an attacker to execute arbitrary commands, potentially leading to unauthorized data access, complete loss of confidentiality and integrity, and significant operational downtime for organizations relying on Flowise for workflow automation.

Immediate Action: Upgrade Flowise to version 2.1.4 or later immediately to remove the vulnerable configuration injection path.

Proactive Monitoring: Review backend Prediction API logs for anomalous overrideConfig payloads or unexpected execution patterns that deviate from standard workflow triggers.

Compensating Controls: Deploy a Web Application Firewall (WAF) with strict rules to inspect and filter incoming JSON payloads for suspicious overrideConfig parameters until the patch is applied.

Public Exploit Available: Unknown

Given the severity of the remote code execution risk, organizations must prioritize patching Flowise instances to version 2.1.4. Failure to remediate this vulnerability leaves the underlying infrastructure exposed to complete takeover by unauthenticated remote actors.