CVE-2025-34267: Flowise: Authenticated Command Execution and Sandbox Bypass via Puppeteer and Playwright Packages
Flowise 3.0.1 up to 3.0.8 lets an authenticated user escape the nodevm sandbox and run commands on the host by pointing the built-in Puppeteer or Playwright modules at attacker-controlled browser binaries. Fixed in flowise 3.0.8, but later versions are still affected if ALLOW_BUILTIN_DEP is enabled.
Published Oct 14, 2025 · Analysis Nov 1, 2026
What an attacker can do
Flowise runs user-written tool code inside a nodevm sandbox. The sandbox can expose built-in modules, among them Puppeteer and Playwright. Those modules launch a browser from a path and with arguments that the caller sets. An authenticated user who can create or run a tool that uses them can set the executable path to a program of their choice, along with its parameters. When the tool runs, Flowise starts that program on the host, outside the sandbox's limits. The result is arbitrary code running as the Flowise process.
The attacker needs a Flowise account with rights to create or run tools (the CVSS 4.0 vector says high privileges, network access, no user interaction). From there they can read the environment, including model API keys and stored credentials, read or change data on the host, and pivot into whatever the host can reach. The vector also marks subsequent-system impact as high.
The advisory text says the problem continues in later versions when ALLOW_BUILTIN_DEP is turned on. The EPSS percentile is high (about 0.94), so this is more likely to be targeted than most entries. No source reports exploitation.
Who is affected
flowise on npm from 3.0.1 up to but not including 3.0.8. The advisory also says all later versions with ALLOW_BUILTIN_DEP enabled are affected. Anyone who can create or run custom tools on the instance is a potential attacker.
npm ls flowise
npm ls -g flowiseFor Docker, check the image tag, and check whether ALLOW_BUILTIN_DEP is set in the environment.
flowise
- Ecosystem
- npm
- Affected
- >= 3.0.1, < 3.0.8
- Fixed in
- 3.0.8
- Check
npm ls flowise
How to fix it
Upgrade to flowise 3.0.8 or later:
npm install -g [email protected]The related pull request 5231 disables built-in dependencies by default and allows them only when ALLOW_BUILTIN_DEP is set to true. Do not set that variable on an instance where users you do not fully trust can write tools. Maintainers noted that custom function nodes can break after the change, and a follow-up (PR 5264) allows node-fetch and axios by default.
The sources name no other workaround. Limit tool creation to trusted users until you update.
How to tell if you were hit
Check the environment for ALLOW_BUILTIN_DEP=true. Review custom tools and function nodes that import puppeteer or playwright and set executablePath, args or similar launch options. On the host, look for child processes of the Flowise Node process that are not a browser, such as shells, curl, or a binary in an upload or temp directory, and for unexpected outbound connections from the Flowise container.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Flowise v3.0.1 < 3.0.8 and all versions after with 'ALLOW_BUILTIN_DEP' enabled contain an authenticated remote code execution vulnerability and node VM sandbox escape due to insecure use of integrated modules (Puppeteer and Playwright) within the nodevm execution environment. An authenticated attacker able to create or run a tool that leverages Puppeteer/Playwright can specify attacker-controlled browser binary paths and parameters. When the tool executes, the attacker-controlled executable/parameters are run on the host and circumvent the intended nodevm sandbox restrictions, resulting in execution of arbitrary code in the context of the host.
NOTE: This vulnerability was incorrectly assigned as a duplicate CVE-2025-26319 and should be considered distinct from that identifier.
Questions
- Is Flowise 3.0.8 or later safe?
The advisory says all versions after the affected range remain exposed when ALLOW_BUILTIN_DEP is enabled. The default now keeps built-in dependencies off, so leave it off unless you need it and trust every tool author.
- Does the attacker need to be logged in?
Yes. They must be an authenticated user able to create or run a tool that uses Puppeteer or Playwright. The CVSS 4.0 vector lists high privileges required.
- Is CVE-2025-34267 the same as CVE-2025-26319?
No. The advisory says CVE-2025-34267 was wrongly marked as a duplicate of CVE-2025-26319 and should be treated as a distinct issue.
References
Read for this analysis:
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-73483
Flowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromium
critical9.4Oct 7, 2026CVE-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, 2026
