CVE-2026-73601

Flowise before 3.1.3 Remote Code Execution via Custom MCP

Published Aug 13, 2026 CVSS 4.0 · 9 Critical EPSS 1.1% KEV · Not listed
Description
Flowise versions before 3.1.3 contain a remote code execution vulnerability in the Custom MCP node when CUSTOM_MCP_PROTOCOL is set to stdio, allowing authenticated users to execute arbitrary commands by manipulating environment variables and command arguments. Attackers can abuse PYTHONWARNINGS and BROWSER environment variables with python3, or leverage the root working directory with node to bypass validation and execute system commands.

Analysis

AI-generated

Technical impact

The vulnerability is a command injection flaw in the Custom MCP node of Flowise, classified under CWE-95. When the CUSTOM_MCP_PROTOCOL environment variable is set to stdio, authenticated users can manipulate environment variables such as PYTHONWARNINGS and BROWSER or the root working directory to execute arbitrary system commands by passing crafted arguments to Python or Node. This flaw allows attackers to gain full code execution, compromising confidentiality, integrity, and availability of the affected system.

Affected Systems

The vulnerable product is FlowiseAI Flowise. All releases before version 3.1.3 are affected; the flaw resides in the Custom MCP node that is invoked when the protocol is configured as stdio.

Risk and Exploitability

The CVSS score of 9 indicates critical severity, and while an EPSS score is not available, the lack of a KEV listing does not reduce the risk. Authenticated attackers can exploit the flaw by sending requests that set malicious environment variables or specify dangerous command arguments, likely through the web or API interface that exposes the Custom MCP node. With remote code execution possible, the vulnerability poses a high likelihood of widespread compromise if not patched.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Flowise to version 3.1.3 or later to eliminate the vulnerability.
  • Temporarily disable or restrict access to the Custom MCP node for authenticated users, especially when the protocol is set to stdio.
  • Implement strict environment variable filtering to disallow PYTHONWARNINGS and BROWSER from being set by users, and sanitise command arguments before execution.

Generated by OpenCVE AI on August 13, 2026 at 12:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Flowise versions before 3.1.3 contain a remote code execution vulnerability in the Custom MCP node when CUSTOM_MCP_PROTOCOL is set to stdio, allowing authenticated users to execute arbitrary commands by manipulating environment variables and command arguments. Attackers can abuse PYTHONWARNINGS and BROWSER environment variables with python3, or leverage the root working directory with node to bypass validation and execute system commands.
Title Flowise before 3.1.3 Remote Code Execution via Custom MCP
First Time appeared Flowiseai
Flowiseai flowise
Weaknesses CWE-95
CPEs cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*
Vendors & Products Flowiseai
Flowiseai flowise
References
Metrics cvssV4_0

{'score': 9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H'}

Weaknesses
  • CWE-95

    Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Aug 14, 2026, 8:18 PM
Reserved
Aug 13, 2026, 11:15 AM
Status
Analyzed
Published
Aug 13, 2026, 12:17 PM
Modified
Oct 24, 2026, 3:10 PM