Live › vulnerability › CVE-2026-119978
Self-hosted Flowise up to 3.1.4 is exposed when ALLOW_BUILTIN_DEP=true and someone with a login or API key can reach /api/v1/node-custom-function. They can write a file into the mammoth package via the langchain LocalFileStore, require it, escape vm2 and run OS commands as the Flowise user (root in the official Docker image). Instances without ALLOW_BUILTIN_DEP=true or without untrusted users can skip it. No fixed version is published yet.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 18:55 UTC. All times on this page are UTC.
Teams running self-hosted Flowise through 3.1.4 where users have accounts. The description says exploitation depends on ALLOW_BUILTIN_DEP=true, so default-configured installs may be less exposed. unknown whether a fixed version exists.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| flowise | npm | <= 3.1.4 | – |
ALLOW_BUILTIN_DEP is set to true in the Flowise environment./api/v1/node-custom-function endpoint is reachable by untrusted users.No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Flowise through 3.1.4 contains a sandbox escape vulnerability that allows authenticated users to execute OS commands by abusing allowlisted langchain and mammoth modules when ALLOW_BUILTIN_DEP=true. Attackers can submit JavaScript to /api/v1/node-custom-function that writes a file into the mammoth package via LocalFileStore and requires it, escaping vm2 as the Flowise process user.
This page as .md · .json · in your agent: get_signal("CVE-2026-119978")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.