Description
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.
Affected products
flowiseai: flowise
References3
- github.com/FlowiseAI/Flowise/security/advisories/GHSA-9rvc-vf7m… ExploitMitigationVendor Advisory
- github.com/FlowiseAI/Flowise/security/advisories/GHSA-9rvc-vf7m… ExploitMitigationVendor Advisory
- github.com/FlowiseAI/Flowise/releases/tag/flowise%403.1.2 ProductRelease Notes
Metrics
- CVSS 3.1
-
9.9
CRITICAL
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - CVSS 4.0
-
9.4
CRITICAL
Score source: CNA
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - EPSS — exploit probability
- 33% percentile: 98 · as of 15 November 2026
- CWE
- CWE-94
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.