CVE-2026-73486: Flowise before 3.1.3 Code Injection via CSV Agent customReadCSV
Flowise before 3.1.3 contains a code injection vulnerability in the CSV Agent node's customReadCSV parameter that allows authenticated attackers to execute arbitrary Python code. The validator uses a static regex blocklist that can be bypassed through obfuscation techniques, enabling attackers to execute code in the unsandboxed pyodide environment with full system access.
Security readout for executives and security teams
Plain-English summary
Authenticated users can abuse Flowise's CSV Agent to run arbitrary Python code on the host. A successful attack could expose data, alter workflows, disrupt service, and compromise connected systems accessible from the Flowise environment.
Executive priority
Treat as an urgent remediation for exposed or multi-user Flowise deployments. Prioritize systems holding sensitive data, credentials, or integrations because successful exploitation could compromise confidentiality, integrity, and availability beyond the application itself.
Technical view
Flowise versions before 3.1.3 inadequately validate the CSV Agent node's customReadCSV parameter. Its static regex blocklist can be bypassed using obfuscation, allowing code injection into an unsandboxed pyodide environment with system access. The issue is classified as CWE-94 and scored CVSS 4.0 9.0.
Likely exposure
Exposure is likely where Flowise before 3.1.3 is deployed and authenticated, potentially untrusted users can configure or use the CSV Agent's customReadCSV parameter. The supplied version metadata is duplicated and internally awkward, so organizations should confirm exact applicability against the vendor advisory.
Exploitation context
The attack is network-accessible but requires low privileges, no user interaction, and high attack complexity. The supplied sources do not establish active exploitation, and the CVE is not identified as being in CISA KEV.
Researcher notes
The security failure is a bypassable regex blocklist applied to code-capable input. Source evidence supports authenticated arbitrary Python execution and broad impact, but does not establish public exploitation, observed attacks, or detailed indicators of compromise. Validate version boundaries with the vendor advisory because the supplied affected-version records are inconsistent.
Mitigation direction
Upgrade affected Flowise deployments to version 3.1.3 or later, following vendor guidance.
Restrict CSV Agent configuration access to trusted administrators until upgrades are complete.
Disable or avoid the CSV Agent customReadCSV functionality where operationally feasible.
Review Flowise service permissions and limit access to sensitive systems and data.
Validation and detection
Inventory Flowise instances and confirm their installed versions.
Identify workflows using the CSV Agent and customReadCSV parameter.
Review authentication roles to determine who can create or modify affected workflows.
Inspect relevant audit and application logs for suspicious CSV Agent changes or unexpected Python execution.
Confirm upgraded instances report version 3.1.3 or later and remain operational.
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.
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
3Source 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-94 · source CWE mapping
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.