CVE-2026-119978 Flowise through 3.1.4 Custom Function Sandbox Escape RCE via LocalFileStore
Critical 9.0
Published
Updated
Check this codebase for CVE-2026-119978 and fix it if it is affected.
What it is: CVE-2026-119978 is a critical vulnerability in FlowiseAI Flowise, published on 30 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-119978 in the wild and no public exploit code.
Affected product: FlowiseAI Flowise. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-119978/ (Markdown: https://insights.sbomify.com/CVE-2026-119978/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-119978?
CVE-2026-119978 is a critical vulnerability in FlowiseAI Flowise, published on 30 Oct 2026.
Official description
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.
Weakness: CWE-749
Which versions are affected by CVE-2026-119978?
How do I fix CVE-2026-119978?
No fix has been published for CVE-2026-119978 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-119978 being exploited?
There is no known exploitation of CVE-2026-119978 in the wild and no public exploit code.
Sources
Also known as GHSA-7pc2-8w3w-pqfg.