Flowise is a drag & drop user interface to build a customized large language model flow. Prior to version 3.1.2, POST /api/v1/node-custom-function lacks route-level authorization, allowing any authenticated user or API key to submit arbitrary JavaScript to the Custom JS Function node. When E2B_APIKEY is not configured — the common deployment case — Flowise executes this code inside a NodeVM sandbox. This sandbox can be escaped, allowing an attacker to reach the host process object and execute system commands via child_process. The result is authenticated remote code execution on the Flowise server host. This issue has been patched in version 3.1.2.

According to its banner, the version of Flowise running on the remote host is < 3.1.2. It is, therefore, affected by multiple vulnerabilities :

- An hardcoded CORS wildcard on TTS endpoint enables abuse from any webpage

- An RCE through Flowise MCP

- A Mass Assignment in Chatflow Update Endpoint

- A Mass Assignment in Tool Update Endpoint

- A Mass Assignment in Assistant Update Endpoint

- A Mass Assignment in Variable Update Endpoint

- A Mass Assignment in PUT /api/v1/user

- An Authenticated Host RCE via POST /api/v1/node-custom-function

- A Cross-Workspace Chatflow Disclosure via chatflows/apikey Endpoint

- A Credential Data Leak

- Vector Store No Permission Checks

- CustomTemplate create+update mass-assignment

- Assistant create+update mass-assignment allows cross-workspace assistant takeover

- DatasetRow create+update mass-assignment

- Dataset create+update mass-assignment

- Evaluation create+update mass-assignment

Note that the scanner has not tested for these issues but has instead relied only on the application's self-reported version number.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - Flowise is a drag & drop user interface to build a customized large language model flow. Prior to version
    3.1.2, POST /api/v1/node-custom-function lacks route-level authorization, allowing any authenticated user
    or API key to submit arbitrary JavaScript to the Custom JS Function node. When E2B_APIKEY is not
    configured — the common deployment case — Flowise executes this code inside a NodeVM sandbox. This sandbox
    can be escaped, allowing an attacker to reach the host process object and execute system commands via
    child_process. The result is authenticated remote code execution on the Flowise server host. This issue
    has been patched in version 3.1.2. (CVE-2026-46442)

ID	Name	Product	Family	Severity
115278	Flowise < 3.1.2 Multiples Vulnerabilities	Web App Scanning	Artificial Intelligence	critical
441880	SCA: security update for flowise (GHSA-9rvc-vf7m-pgm2)	Tenable Cloud Security	SCA Checks	critical
441880	SCA: security update for flowise (GHSA-9rvc-vf7m-pgm2)	Tenable Self-Hosted Container Security	SCA Checks	critical

Detections

Analytics

CVE-2026-46442

critical

Tenable Plugins

critical

critical

critical