Browse / AI Framework and Platform Flaws / CVE-2026-119978
Flowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromium
- Class
- AI Framework and Platform Flaws (filed by a model that read the advisory)
- Technique
- Sandbox escape
- Affected
- flowise-components, flowise (npm)
- Gets past
- Sandbox or allowlist
- CVSS
- 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
- EPSS
- 0.3% chance of exploitation in 30 days
How it works, in short
An authenticated user passes executable path and args to puppeteer.launch from the sandboxed custom function, spawning host commands outside the sandbox. (Our summary, written by a model. The source text is below.)
Details
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.
References
- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-9gvv-qjj3-2p6g
- https://nvd.nist.gov/vuln/detail/CVE-2026-73483
- https://github.com/FlowiseAI/Flowise
- https://www.vulncheck.com/advisories/flowise-before-sandbox-escape-via-puppeteer
Source: GitHub Advisory Database, used under CC BY 4.0.