Security readout for executives and security teams
Plain-English summary
Flowise versions before 3.1.3 can allow malicious CSV content to escape into Python execution through the CSV Agent. Successful exploitation can run operating-system commands with root privileges inside the Flowise container, risking complete compromise of its data, credentials, and availability.
Executive priority
Prioritize emergency remediation for exposed or multi-user Flowise deployments using the CSV Agent. Root-level container command execution creates a credible path to service takeover and sensitive-data loss. Upgrade promptly, restrict CSV ingestion until complete, and investigate potentially exposed instances.
Technical view
CSVAgent inserted attacker-controlled CSV-derived data into a quoted Python assignment without safe encoding before Pyodide execution. An attacker could terminate the string, inject Python, and reach Node.js command execution through Pyodide’s JavaScript bridge. The Python denylist did not inspect this initial block. Version 3.1.3 fixes the issue.
Likely exposure
Exposure is limited to Flowise versions earlier than 3.1.3 where the CSV Agent processes attacker-controlled CSV data. Internet or broadly accessible deployments are especially concerning. The bundle describes an authenticated attacker, although its CVSS vector states no privileges required; access prerequisites should therefore be verified locally.
Exploitation context
Root command execution inside a Flowise container was reportedly verified, demonstrating practical impact. However, the supplied evidence does not establish exploitation in the wild, and the CVE is not identified as KEV-listed. Treat exploitability as demonstrated but active campaigns as unconfirmed.
Researcher notes
The vulnerable trust boundary precedes the existing validation control: CSV-derived content entered the initial executable Python block, while validation covered only later LLM-generated code. CWE-94 is appropriate. Authentication requirements are inconsistent between the narrative and CVSS vector, so assess both authenticated and unauthenticated reachability without assuming either.
Mitigation direction
- Upgrade Flowise to version 3.1.3 or later.
- Until upgraded, prevent untrusted users from submitting CSV data to the CSV Agent.
- Restrict access to affected Flowise deployments and review vendor guidance.
- Rotate credentials accessible to the container if compromise is suspected.
Validation and detection
- Confirm every Flowise instance reports version 3.1.3 or later.
- Inventory flows using the CSV Agent and identify who can supply CSV data.
- Verify the deployed build includes the referenced security fix.
- Review affected containers for unexpected processes, commands, file changes, or credential access.
- Confirm access controls prevent unauthorized CSV Agent use.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupExecution behavior lookup
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.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-69255 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.2 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
9.2CriticalVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-vmv7-4m6c-3cg5CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/FlowiseAI/Flowise/pull/6499CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/FlowiseAI/Flowise/commit/f4e2794f6a576b94578f2fdafbf49c2fb304626cCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/FlowiseAI/Flowise/releases/tag/flowise%403.1.3CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.