CVE-2026-69264
Unauthenticated RCE in Flowise CSVAgent via crafted csvFile (fixed in 3.1.3).
Is CVE-2026-69264 being exploited?
Not confirmed. CVE-2026-69264 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.2% probability of exploitation in the next 30 days.
How severe is CVE-2026-69264?
CVE-2026-69264 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-69264?
Yes. A fix has been recorded for CVE-2026-69264. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-69264 affect?
CVE-2026-69264 affects Flowise < 3.1.3, Flowise CSVAgent, Deployments exposing /api/v1/prediction/:id. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-69264?
Upgrade to Flowise 3.1.3 immediately; restrict access and revoke risky workspace permissions.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote code execution as the Flowise process: attackers can run OS commands, read/write files, and spawn processes via Pyodide/Node bridge.
Immediate action required
- affected< 3.1.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.