Is CVE-2026-119978 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-119978 being exploited in the wild.

How severe is CVE-2026-119978?

High severity, with a CVSS score of 8.5, published 30 October 2026.

Which products and versions are affected?

FlowiseAI Flowise through 3.1.4.

Is there a fix for CVE-2026-119978?

No fixed version is recorded yet. Disable the ALLOW_BUILTIN_DEP environment variable if not required for your deployment, or upgrade to a patched version once available. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-119978 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-119978?

Check whether you run FlowiseAI Flowise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-119978: Flowise sandbox escape in custom function endpoint

CVE-2026-119978 · Severity: high · CVSS 8.5 · Published 2026-10-30

Flowise, a low-code platform for building AI agents, contains a sandbox escape vulnerability that allows authenticated users to execute arbitrary operating system commands. An attacker with access to the application can submit malicious code to the custom function endpoint, bypass the JavaScript sandbox, and execute commands with the privileges of the Flowise process, potentially leading to complete system compromise.

Technologies: FlowiseAI Flowise. Vendors: FlowiseAI.

Quick answers

Is CVE-2026-119978 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-119978 being exploited in the wild.
How severe is CVE-2026-119978?: High severity, with a CVSS score of 8.5, published 30 October 2026.
Which products and versions are affected?: FlowiseAI Flowise through 3.1.4.
Is there a fix for CVE-2026-119978?: No fixed version is recorded yet. Disable the ALLOW_BUILTIN_DEP environment variable if not required for your deployment, or upgrade to a patched version once available. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-119978 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-119978?: Check whether you run FlowiseAI Flowise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Disable the ALLOW_BUILTIN_DEP environment variable if not required for your deployment, or upgrade to a patched version once available.

Technical details

The vulnerability is a sandbox escape in vm2 affecting Flowise through 3.1.4 when ALLOW_BUILTIN_DEP is enabled. Authenticated attackers can exploit the /api/v1/node-custom-function endpoint by injecting JavaScript that abuses allowlisted langchain and mammoth modules; the attacker writes a malicious file into the mammoth package directory via LocalFileStore and requires it, breaking out of the vm2 sandbox and achieving remote code execution as the Flowise process user.

Affected products

FlowiseAI Flowise through 3.1.4

Timeline

2026-10-30: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.