CVE-2026-69253

Flowise Sandbox Escape to RCE

Published Aug 4, 2026 CVSS 4.0 · 9 Critical EPSS < 1% KEV · Not listed
Description
Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. Prior to version 3.1.3, several custom-tool components — AgentAsTool, ChatflowTool, and ExecuteFlow — ran code in the in-process  vm2  sandbox. To build that code, they inserted a user-controlled  baseURL  value straight into the JavaScript source, for example  const url = "${baseURL}/..."; . The only check on  baseURL  was  isValidURL , but a valid-looking URL can still contain characters that break out of a code string. An authenticated user could craft a  baseURL  that passed this check, closed the surrounding string, and injected their own JavaScript into the sandboxed script (code injection, CWE-94). The  vm2  sandbox runs in the same Node.js process as Flowise and exposes risky dependencies. As a result, the injected code could escape the sandbox and run arbitrary code on the Flowise server as the Flowise process user. Exploitation only requires an authenticated session. The issue is fixed in version 3.1.3, which passes the URL to the sandbox as data instead of inserting it into code and adds stricter URL validation.

Analysis

AI-generated

Technical impact

A vulnerability in Flowise allows an authenticated user to inject arbitrary JavaScript into code that is executed within the vm2 sandbox. User‑controlled baseURL values are inserted directly into a JavaScript string without sufficient escaping, enabling the injection of malicious code. The injected code can escape the sandbox and run as the Flowise process user, providing full control of the server. This results in Remote Code Execution with the privileges of the Flowise service. The weakness is a form of code injection, identified as CWE-95.

Affected Systems

The affected product is Flowise by FlowiseAI. Versions prior to 3.1.3 are vulnerable. The issue was addressed in release 3.1.3, which passes the baseURL as data into the sandbox and tightens URL validation. Users running any deployment of Flowise 3.1.2 or earlier are at risk.

Risk and Exploitability

The CVSS score of 9 indicates a high‑severity vulnerability. No EPSS score is available, and the flaw is not listed in CISA’s KEV catalog. Exploitation requires an authenticated session and the ability to configure custom‑tool components, but otherwise offers complete server compromise. Attackers can target organizations that host Flowise or provide hosted Flowise services, as the vulnerability exists in the code that runs on the server side.

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 code injection path.
  • Restrict access to custom‑tool configuration pages to trusted administrators until the patch is applied.
  • Monitor system logs for anomalous JavaScript execution or attempts to bypass sandbox restrictions, and investigate any suspicious activity promptly.

Generated by OpenCVE AI on August 4, 2026 at 19:41 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-wg86-r78f-74mp Flowise Sandbox Escape to RCE
History
Type Values Removed Values Added
CPEs cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*
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
First Time appeared Flowiseai
Flowiseai flowise
Vendors & Products Flowiseai
Flowiseai flowise
Type Values Removed Values Added
Description Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. Prior to version 3.1.3, several custom-tool components — AgentAsTool, ChatflowTool, and ExecuteFlow — ran code in the in-process  vm2  sandbox. To build that code, they inserted a user-controlled  baseURL  value straight into the JavaScript source, for example  const url = "${baseURL}/..."; . The only check on  baseURL  was  isValidURL , but a valid-looking URL can still contain characters that break out of a code string. An authenticated user could craft a  baseURL  that passed this check, closed the surrounding string, and injected their own JavaScript into the sandboxed script (code injection, CWE-94). The  vm2  sandbox runs in the same Node.js process as Flowise and exposes risky dependencies. As a result, the injected code could escape the sandbox and run arbitrary code on the Flowise server as the Flowise process user. Exploitation only requires an authenticated session. The issue is fixed in version 3.1.3, which passes the URL to the sandbox as data instead of inserting it into code and adds stricter URL validation.
Title Flowise Sandbox Escape to RCE
Weaknesses CWE-95
References
Metrics cvssV4_0

{'score': 9, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:N/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
GitHub_M
Published
Updated
Aug 5, 2026, 2:42 PM
Reserved
Aug 3, 2026, 7:54 PM
Status
Analyzed
Published
Aug 4, 2026, 4:16 PM
Modified
Oct 23, 2026, 11:10 PM