CVE-2026-69254: Flowise: RCE via NodeVM Sandbox Escape in executeJavaScriptCode() nodeVMOptions Override
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, executeJavaScriptCode() accepted caller-provided nodeVMOptions and merged them over the default NodeVM security settings in packages/components/src/utils.ts. An authenticated attacker reaching packages/server/src/routes/node-custom-functions/index.ts could run a custom function that imported flowise-components/dist/src/utils.js, called executeJavaScriptCode() again with nodeVMOptions.require.builtin set to allow all built-in modules, and then required child_process to execute arbitrary system commands as root on the Flowise server. This issue is fixed in version 3.1.3.
Security readout for executives and security teams
Plain-English summary
An authenticated attacker with access to Flowise custom functions could escape a JavaScript sandbox and take complete control of a vulnerable server. Successful abuse could expose data, alter workflows, disrupt service, and compromise connected systems. Flowise versions before 3.1.3 are affected.
Executive priority
Treat as an immediate remediation priority. Identify exposed Flowise systems, upgrade them promptly, and restrict custom-function access while remediation proceeds. Because successful exploitation can provide root-level server control, investigate vulnerable systems for compromise rather than assuming an upgrade alone resolves prior exposure.
Technical view
Caller-controlled nodeVMOptions could override executeJavaScriptCode() security defaults. Through the authenticated custom-functions route, an attacker could expand permitted Node.js modules and escape the intended NodeVM restrictions, resulting in arbitrary operating-system command execution as root. This is CWE-94 and carries a CVSS 4.0 score of 9.4.
Likely exposure
Exposure is highest where Flowise before 3.1.3 is network-accessible and untrusted or weakly governed accounts can reach custom-function capabilities. Internet exposure increases attack opportunity, but authentication is required. The supplied sources do not establish how commonly this route is enabled or accessible in deployments.
Exploitation context
The vulnerability requires low privileges, network access, no user interaction, and low attack complexity. The source bundle reports no CISA KEV listing and provides no evidence of active exploitation. Public disclosure may nevertheless increase near-term probing and exploitation interest.
Researcher notes
The security boundary failed because untrusted options were merged over NodeVM defaults. The described path involves an authenticated custom function reusing an internal utility with weakened module restrictions. The supplied commit, pull request, advisory, and 3.1.3 release identify the correction, but the bundle does not document observed attacks or deployment prevalence.
Mitigation direction
Upgrade Flowise to version 3.1.3 or later using official release guidance.
Restrict custom-function access to trusted administrators until upgrading is complete.
Limit network access to Flowise management and authoring interfaces.
Rotate sensitive credentials if server compromise is suspected.
Review vendor guidance for any additional containment or recovery recommendations.
Validation and detection
Inventory all Flowise instances and confirm their installed versions.
Verify no production instance runs a version earlier than 3.1.3.
Review account permissions for access to custom-function capabilities.
Examine server and application logs for unexpected child processes or privileged command execution.
Confirm Flowise interfaces are exposed only to intended networks and users.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.