GPU VulnDB

Database/AI/ML frameworks & serving

Flowise: custom-function sandbox escape gives authenticated users OS command execution

CVSS 9.0CVE-2026-119978AI/ML frameworks & servingcurated

Impact

Flowise runs user-authored JavaScript for LLM flows inside a vm2 sandbox. With ALLOW_BUILTIN_DEP=true, an authenticated user can post JavaScript to /api/v1/node-custom-function that uses LocalFileStore to write a file into the allowlisted mammoth package and then require it, executing outside the sandbox as the Flowise process user. On a shared inference host that means OS command execution with whatever the Flowise service account holds - model files, API keys for upstream model providers, and network reach to the rest of the serving tier. Anyone who can log in and build a flow, which in most deployments is every user of the tool, gets this.

Who can reach it

Any authenticated Flowise user who can submit a custom function, over the network to the Flowise API. Requires ALLOW_BUILTIN_DEP=true; low privilege otherwise.

What to do

No fixed version is named in the record - it reports Flowise affected through 3.1.4. Set ALLOW_BUILTIN_DEP=false and restart the Flowise service, which removes the allowlisted-module path this abuses, and restrict who can author custom functions. Treat the Flowise process credentials as exposed on any instance that ran with the flag on. Patching is a daemon restart, not a node operation.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.