CVE-2026-73483: Flowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromium
Flowise 3.1.2 and earlier let an authenticated user escape the NodeVM sandbox on /api/v1/node-custom-function through puppeteer.launch() with attacker-set executablePath and args. That runs OS commands as the Flowise user, root in the official Docker image, and reads host files through Chromium. Fixed in 3.1.3.
Published Oct 7, 2026 · Analysis Oct 28, 2026
What an attacker can do
The custom function node runs user JavaScript inside the vm2-based @flowiseai/nodevm sandbox, with some built-in dependencies allowed. Puppeteer is on that allowlist. The attacker supplies their own executablePath and args to puppeteer.launch(), and puppeteer calls child_process.spawn() outside the sandbox boundary. That is a direct path to arbitrary commands.
The same trick also reads host files: Chromium opens file:// URLs, so files on the server can be pulled out through a page load.
The attacker needs an account that can call /api/v1/node-custom-function; the CVSS 4.0 vector shows low privileges. In the official Docker image Flowise runs as root, so the commands run as root. The impact reaches stored API keys, model provider credentials and anything on the host or network the container can reach.
From 3.0.8 to 3.1.2, the attack needs ALLOW_BUILTIN_DEP=true. Releases before 3.0.8 are exploitable by default.
Who is affected
The npm packages flowise and flowise-components at 3.1.2 and earlier. Versions before 3.0.8 are exploitable by default. In 3.0.8 through 3.1.2 the instance must have ALLOW_BUILTIN_DEP=true set.
npm ls flowise flowise-componentsFor Docker, read the image tag, then check the environment for the setting:
docker exec <container> printenv ALLOW_BUILTIN_DEPflowise
- Ecosystem
- npm
- Affected
- <= 3.1.2
- Fixed in
- 3.1.3
- Check
npm ls flowise
flowise-components
- Ecosystem
- npm
- Affected
- <= 3.1.2
- Fixed in
- 3.1.3
- Check
npm ls flowise-components
How to fix it
Upgrade flowise and flowise-components to 3.1.3:
npm install -g [email protected]The advisory lists no workaround beyond that. Leaving ALLOW_BUILTIN_DEP unset on 3.0.8 to 3.1.2 stops the attack on those releases, according to the advisory's condition, but it does not help older ones. Do not run Flowise as root, and limit which accounts can reach node-custom-function.
How to tell if you were hit
Search Flowise access logs for POST requests to /api/v1/node-custom-function from unexpected accounts. Look for Chromium or other processes spawned by the Flowise process with unusual executable paths and arguments, especially --no-sandbox or file:// targets. Review saved custom function nodes for puppeteer.launch with executablePath. Beam records shell commands that agents and tools run on the host.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to Skaushik-Qlys.
Questions
- Does the attacker need a login?
Yes. The advisory says an authenticated user with access to /api/v1/node-custom-function. The CVSS 4.0 vector shows low privileges required.
- Does ALLOW_BUILTIN_DEP=true matter?
In 3.0.8 through 3.1.2 exploitation requires it. Earlier versions are exploitable by default.
- What is the fixed version?
3.1.3, for both flowise and flowise-components.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More Flowise vulnerabilities
All Flowise entriesCVE-2026-73487
Flowise Prompt Injection to RCE and SSRF via CSV/Airtable Agent Python Validator Bypass
critical9.0Oct 7, 2026CVE-2026-69250
Flowise: Unauthenticated OAuth2 Refresh Enables Non-Blind SSRF and Secret Exfiltration
high8.5Aug 4, 2026CVE-2026-69251
Flowise RCE via TypeORM DataSource
critical9.0Aug 4, 2026CVE-2026-69252
Flowise: Missing authorization on `/api/v1/files` allows low-privileged API keys to list and delete files across workspaces within the same organization
high7.2Aug 4, 2026CVE-2026-69253
Flowise Sandbox Escape to RCE
critical9.0Aug 4, 2026CVE-2026-69254
Flowise: RCE via NodeVM Sandbox Escape in executeJavaScriptCode() nodeVMOptions Override
critical9.4Aug 4, 2026
