Description
Flowise (packages flowise and flowise-components) in versions <= 3.1.2 contain a sandbox escape in the vm2/@flowiseai/nodevm JavaScript sandbox. An authenticated user with access to the /api/v1/node-custom-function endpoint can escape the sandbox by supplying attacker-controlled executablePath and args parameters to puppeteer.launch(), which internally invokes child_process.spawn() outside the sandbox boundary. This allows execution of arbitrary OS commands as the Flowise process user (root in the official Docker image) and arbitrary host file disclosure via Chromium's file:// URL handling. In versions 3.0.8–3.1.2 exploitation requires ALLOW_BUILTIN_DEP=true; earlier versions are exploitable by default. Fixed in 3.1.3.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| FlowiseAI | Flowise | < 3.1.3 | 3.1.3 |
Advisories 1
- WID-SEC-2026-2589 Flowise: Mehrere Schwachstellen BSI CERT-Bund (WID) · Sep 9, 2026
References
- GitHub Security Advisory (GHSA-9gvv-qjj3-2p6g) vendor-advisory
- VulnCheck Advisory: Flowise before 3.1.3 Sandbox Escape via Puppeteer third-party-advisory