Flowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromium

[ Why it matters ]Priority signals

• Public proof-of-concept exploit exists (CISA SSVC)
• Critical severity: CVSS 9.4

[ Description ]Official 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.

[ Fixes ]Fixes and patches

• flowise 3.1.3Fixed version · GitHub Advisories · npm package flowise: upgrade to 3.1.3 or later (affected <= 3.1.2)
• flowise-components 3.1.3Fixed version · GitHub Advisories · npm package flowise-components: upgrade to 3.1.3 or later (affected <= 3.1.2)

[ Packages ]Affected open-source packages

• flowise npmAffected <= 3.1.2 · fixed in 3.1.3 · GHSA-9gvv-qjj3-2p6g
• flowise-components npmAffected <= 3.1.2 · fixed in 3.1.3 · GHSA-9gvv-qjj3-2p6g

[ References ]References

• github.com/FlowiseAI/Flowise/security/advisories/GHSA-9gvv-qjj3-2p6gvendor-advisory
• www.vulncheck.com/advisories/flowise-before-sandbox-escape-via-puppeteerthird-party-advisory