Flowise: RCE via CSVAgent csvFile data URI base64 segment is interpolated into Python source without validation
CVE-2026-69264 · GHSA-4j8x-x6v7-w9rq · published 2026-08-04
- Severity
- Critical
- CVSS score
- 9.4
- Chance of exploitation (EPSS)
- 1.1%
- Fixed in
- 3.1.3
- Exploitation Public proof of concept
- Automatable No
- Technical impact Total
- CISA SSVC
Class: Remote Code Execution via Python-template injection escaping the Pyodide sandbox through the js bridge. Affected: every Flowise deployment that exposes a chatflow containing a CSVAgent node where csvFile is operator-supplied (i.e., overridable via nodeOverrides for the API caller, or planted by any user with chatflow edit permission). Prerequisites: one user with chatflows:create / chatflows:update / agentflows:create / agentflows:update to plant the chatflow once. The trigger is unauthenticated when the chatflow has no apikeyid set (the default for newly created chatflows). Result: arbitrary OS-command execution as the Flowise process.
Upgrade flowise to 3.1.3 or later, and flowise-components to 3.1.3 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Maintainer fix (preferred — eliminates string-interpolation entirely): pass the base64 value through Pyodide's globals.set API instead of template-string interpolation. In , replace the construction at lines 156–171 with something like: This keeps the value as a Python str object that never enters the source text. Apply the same change to AirtableAgent.ts if it follows the same pattern. Defense in depth (recommended as well): 1. 2. Disable Pyodide's js module on load. Pyodide supports loadPyodide({ jsglobals: {} }) or the js-module-removal recipe; either prevents the bridge to globalThis.process on Node.js.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| flowise | npm | <= 3.1.2 | 3.1.3 |
| flowise-components | npm | <= 3.1.2 | 3.1.3 |
- CriticalUnauthenticated Remote Code Execution in Langflow via Public Flow Build EndpointlangflowExploited
- CriticalRay is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding AttackrayExploited
- CriticalLangflow Unauth RCElangflow, langflow-baseExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalAgno: Arbitrary code execution via `eval()` on `field_type` in `FunctionCall`agno
- CriticalFlowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromiumflowise, flowise-components
- CriticalFlowise Prompt Injection to RCE and SSRF via CSV/Airtable Agent Python Validator Bypassflowise, flowise-components
- CriticalCross-IdP account takeover via email-only SSO matchingflowise
- CriticalINVITED users auto-promoted via SSO email match (invite-token bypass)flowise
- CriticalSSRF + LLM API key exfiltration via user-controlled basepath / baseUrl in 8 chat-model nodesflowise, flowise-components
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.