← All advisories
CVE-2026-119978highCode execution2026-10-30

CVE-2026-119978: Flowise through 3.1.4 lets logged-in users escape the custom-function sandbox and run OS commands when ALLOW_BUILTIN_DEP=true

Flowise through 3.1.4 has another vm2 sandbox escape in its custom JavaScript function endpoint. With ALLOW_BUILTIN_DEP=true, an authenticated user can abuse the allowlisted langchain and mammoth modules to write a file into the mammoth package and load it, running OS commands as the Flowise process user. NVD lists no fixed version.

01.

What it is

The endpoint /api/v1/node-custom-function runs user JavaScript inside vm2 with an allowlist of modules.

When ALLOW_BUILTIN_DEP=true, an attacker can use the allowlisted langchain LocalFileStore to write a file into the mammoth package and then require it, escaping vm2 (CWE-749).

The code then runs as the Flowise process user. The attacker needs to be an authenticated Flowise user.

02.

How to check

  1. Check your Flowise version (3.1.4 and earlier are affected according to NVD).
  2. Check whether ALLOW_BUILTIN_DEP is set to true in your Flowise environment or docker-compose file.
03.

How to fix

  1. Set ALLOW_BUILTIN_DEP to false (or remove it) unless you truly need built-in modules in custom functions.
  2. Limit who can log in to Flowise and keep it off the public internet.
  3. Watch the Flowise releases for a version that names this CVE as fixed and upgrade when it ships.
# look for the risky setting
grep -rn ALLOW_BUILTIN_DEP .env docker-compose*.yml 2>/dev/null
04.

Sources

More advisories for this tool
The weekly email

One email a week. Only what changed.

Every new security hole in AI coding tools, MCP servers, app builders and the stacks they generate (Next.js, Supabase, Node, PHP), each with how to check your app and the fix. No roundups of things you already read.

Free, one email a week. Read the latest issue first if you like. One-click unsubscribe in every email. We never sell or share addresses.