CVE-2026-69264: Flowise: RCE via CSVAgent csvFile data URI base64 segment is interpolated into Python source without validation
Prior to 3.1.3, Flowise CSVAgent interpolates an attacker-controlled segment of the csvFile data URI directly into a Python source-code template that is then executed by Pyodide. Because Pyodide is loaded with the default js bridge to globalThis, which on Node.js exposes eval and dynamic import, the attacker can break out of the Python string literal, hand a JavaScript string to js.eval, dynamically import Node built-in modules such as fs and child_process, and execute arbitrary file I/O or OS commands as the Flowise process. The two validator paths around this code, validatePythonCodeForDataFrame and validateCustomReadCSVFunction, are never applied to the bootstrap template. A workspace user with chatflows:create or agentflows/chatflows update permission can plant a CSV Agent node with a crafted csvFile; once the chatflow is exposed via POST /api/v1/prediction/:id, any unauthenticated request triggers host remote code execution. This issue is fixed in version 3.1.3.
Security readout for executives and security teams
Plain-English summary
Flowise versions before 3.1.3 allow a permitted workspace user to hide malicious content inside a CSV Agent configuration. When anyone later calls the published chatflow prediction endpoint, Flowise can execute that content with the server process’s privileges, potentially exposing files, credentials, connected systems, and service availability.
Executive priority
Treat this as an immediate patching and access-review priority for affected Flowise deployments. A malicious or compromised workspace account could establish server-level code execution that is subsequently triggered without authentication. Prioritize internet-accessible prediction endpoints and environments where Flowise holds sensitive credentials or reaches critical systems.
Technical view
CSVAgent inserts an attacker-controlled csvFile data-URI segment into executable Python source without validating the bootstrap template. Pyodide’s default JavaScript bridge can expose Node.js capabilities, enabling arbitrary file access and operating-system command execution. Planting the payload requires chatflow creation or update permission; triggering an exposed flow may require no authentication.
Likely exposure
Flowise deployments below 3.1.3 are affected. Highest risk exists where untrusted or compromised workspace users can create or update chatflows and CSV Agent flows are exposed through POST /api/v1/prediction/:id. Exposure cannot be determined from version alone; permissions, flow configuration, endpoint accessibility, and prior modifications must be reviewed.
Exploitation context
The supplied sources describe a credible remote-code-execution path with low attack complexity and no user interaction after configuration. Initial placement requires limited workspace privileges, but an unauthenticated request can trigger a planted exposed flow. The CVE is not listed as KEV in the supplied bundle, and no evidence of active exploitation is provided.
Researcher notes
The vulnerable bootstrap path bypasses both named Python validators. The impact depends on Pyodide’s bridge to globalThis and Node.js dynamic imports, allowing execution in the Flowise process context. Defensive review should focus on affected versions, CSV Agent configuration history, privileged workspace activity, exposed prediction routes, and host-level indicators; the supplied evidence does not establish exploitation in the wild.
Mitigation direction
Upgrade Flowise to version 3.1.3 or later.
Restrict chatflow creation and update permissions to trusted administrators.
Disable or unpublish affected CSV Agent flows until upgrading.
Limit prediction endpoint access while investigating potentially exposed flows.
Rotate credentials if evidence suggests the Flowise process was compromised.
Validation and detection
Confirm every Flowise deployment reports version 3.1.3 or later.
Inventory CSV Agent nodes and identify externally accessible prediction endpoints.
Review workspace roles for chatflow creation or update permissions.
Inspect recent chatflow changes for unexpected csvFile data URIs.
Review process, file-access, and child-process telemetry for anomalous Flowise activity.
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.
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 file access or upload behavior, so file telemetry and web shell 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.