CVE-2026-46442
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.
Does this matter?
EPSS puts the probability of exploitation in the next 30 days at 36.3%, higher than 98% of all known CVEs. Patch or mitigate before the next change window.
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.
- CVSS 4.0
- 9.4 CRITICALCVSS: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/M
- EPSS
- 36.34% probability · 98th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-94
- Affected
- flowiseai/flowise
- Source
- security-advisories@github.com
References
- https://github.com/FlowiseAI/Flowise/releases/tag/flowise%403.1.2Product, Release Notes
- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-9rvc-vf7m-pgm2Exploit, Mitigation, Vendor Advisory
- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-9rvc-vf7m-pgm2Exploit, Mitigation, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.