Skip to content

AAK-FLOWISE-CVE-2026-119978-001: Flowise from 1.4.6, every release (no fix, the project has ended): the custom function sandbox lets a caller write a file into an allowed package and run it

Severity
HIGH
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
FlowiseCustomFunctionAllowlistWrite

What it detects

Flowise (flowise on npm), a low-code builder for LLM apps and agents, runs the JavaScript a caller posts to /api/v1/node-custom-function in vm2's NodeVM, and lets that code require the packages on flowise-components' availableDependencies list. vm2 matches an allowed name as the whole package folder and loads the package in the host process, so the code can use langchain's LocalFileStore (langchain/storage/file_system) to write a file into the folder of mammoth, another allowed package with no exports map, and then require that file, which Node runs as JavaScript: OS commands as the Flowise process user (CVE-2026-119978, CVSS 8.5, CWE-749). It takes credentials that may create or update chatflows. Checked in the npm tarballs: the route first ships in 1.4.6 (2023-12-18), beside flowise-components 1.4.7, which added the CustomFunction node a minute earlier, and 1.4.5 has neither. Every flowise-components release from 1.4.7 to 3.1.4 puts both packages on the list, with no setting needed through 3.0.7 and only with ALLOW_BUILTIN_DEP=true from 3.0.8. There is no fixed release and FlowiseAI will not ship one: 3.1.4 (2026-07-29) is the last, the repository was archived on 2026-08-13 and the project ended on 2026-08-31. The flaw is in the custom function sandbox, not in Flowise's MCP nodes.

How to fix

There is no fixed version, and FlowiseAI will ship none. On 3.0.8 or later leave ALLOW_BUILTIN_DEP unset or false, which takes the package list out of the sandbox, and add nothing to TOOL_FUNCTION_EXTERNAL_DEP that can write files; before 3.0.8 no setting closes it. Give the permissions that create or update chatflows and agentflows only to people you would trust with a shell on the server, keep the Flowise API off networks you do not trust, and plan the move off Flowise, or onto a fork that removes the package list from the custom function sandbox.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-FLOWISE-CVE-2026-119978-001

Limitations

Reports an npm reference to flowise from 1.4.6, with or without a version, since every later release is affected and none is fixed: flowise in package.json, .mcp.json, mcp.json and claude_desktop_config.json, and the package-lock.json, pnpm-lock.yaml and yarn.lock lockfiles, at the project root only, reporting a range that admits 1.4.6 or later. 1.4.5 and earlier had no custom function route and are not reported. The dependency is not read when it is declared in a sub-directory manifest (packages/app/package.json). flowise-components, which ships the allowlist, is not read: the CVE record names Flowise alone, and only the finder's write-up names the components package. Releases before 1.6.1 declare flowise-components as *, so their own version does not say which components release runs beside them. The flowiseai/flowise image tag is not read, in a compose file or in an MCP config that starts it with docker run. It reads the version, not the server's settings, so from 3.0.8 a server without ALLOW_BUILTIN_DEP=true is reported too. PyPI's flowise (FlowiseAI's Python SDK) is not matched. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-FLOWISE-CVE-2026-119978-001.md: the page then shows that text, with the registry reference appended under it.