CVE-2026-69255 is an improper control of code generation vulnerability in Flowise versions prior to 3.1.3. The CSVAgent component incorporated attacker-controlled CSV-derived data directly into a Python string that was executed by Pyodide. Its validation logic applied only to subsequently generated LLM code and did not inspect this initial Python block. A crafted value can terminate the intended Python string context and inject arbitrary Python. The injected code can use Pyodide's JavaScript bridge to access Node.js capabilities, including process-execution functionality.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Arbitrary code execution vulnerability in the Flowise CSVAgent component via Python code injection, with published evidence showing elevated shell access inside the Flowise container.
A code injection vulnerability in Flowise CSVAgent that allows an attacker to inject Python code via attacker-controlled CSV data and achieve arbitrary OS command execution as root in the Flowise container.
Critical code-injection vulnerability in Flowise CSVAgent that permits arbitrary OS command execution as root in the Flowise container via malicious CSV input. Fixed in Flowise version 3.1.3.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.