Vulnerability report

Active exploitation observed Confirmed confidence Not in CISA KEV

CVE-2026-69255

Flowise CSV Agent Remote Code Execution

FlowiseAI / Flowise · affected before 3.1.3

View live feed Monitor via API Watch CVE-2026-69255
Severity
CVSS 9.2 · Critical
Confidence
Confirmed
Exploit status
Observed in sensors
EPSS
0.6%
First observed
18 Aug 2026
Last observed
15 Sep 2026

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2026-69255 is an unauthenticated vulnerability affecting FlowiseAI Flowise. Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, the CSVAgent in...

Is it exploited?

Yes. Previdian sensors observed exploitation attempts with confirmed confidence.

Who is affected?

FlowiseAI / Flowise affected before 3.1.3.

What should we do?

Patch immediately, validate internet-facing exposure, and monitor for matching requests.

Overview

Flowise is a drag & drop user interface to build a customized large language model flow

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, the CSVAgent in packages/components/nodes/agents/CSVAgent/CSVAgent.ts extracted attacker-controlled CSV data with file.split(',').pop() and interpolated it directly into executable Python as base64_string = "${base64String}" before calling Pyodide. The validatePythonCodeForDataFrame() denylist only checked later LLM-generated code and did not validate this initial code block.

An authenticated attacker could inject a closing quote followed by Python code, use Pyodide's js bridge to load Node.js child_process, and execute arbitrary operating system commands as root in the Flowise container. This issue is fixed in version 3.1.3.

FlowiseAI Affected
Flowise
Before 3.1.3
Published
04 Aug 2026
Exploitation Reported
18 Aug 2026
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

nodejs python

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

Previdian

Recorded 18 Aug 2026

Previdian independently recorded this as exploited after first seeing it in honeypot sensors.

Active exploitation observed

Previdian sensor

First observed 18 Aug 2026

Previdian first observed exploitation attempts targeting this vulnerability in our honeypot sensors.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
Previdian First 2026-09-15 19:57 UTC

Operational indicators for this CVE are listed under Detection.

Sensor telemetry

First-party evidence of exploitation activity

Previdian sensors recorded exploitation attempts targeting this vulnerability. The cards and chart show volume, unique attackers, and daily activity.

2

Attempts observed

1

Unique attacker IPs

1

Attacker countries

SG

1

Sensors observed

CVE-2026-69255 exploitation attempts over the last 32 days

Daily events observed by Previdian sensors

Updated 17 Sep 2026

0
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2
0
0
17 Aug 24 Aug 31 Aug 7 Sep 17 Sep

First observed 18 Aug 2026 · Last observed 15 Sep 2026

Pro adds sensor region and window summaries. Enterprise adds raw IPs, paths, User-Agents, and payloads.

Request telemetry access

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
1
1
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Attacker IP Indicators

Attacker IP indicators observed · available in Pro and Enterprise.

Sensor-derived attacker IP indicators are available to Pro and Enterprise accounts under Detection and through the Pro API.

Learn about Pro API access

Risk and context

Severity, weaknesses, and research context

CVSS v4.0

9.2 Critical
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

EPSS

0.6%

Weaknesses

Improper Control of Generation of Code ('Code Injection') CWE-94

All CVSS Scores

CVSS v4.0 9.2 Critical

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

CVSS v3.1 8.8 High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Timeline

From disclosure to observed exploitation

  1. 08:09 UTC

    Indicators of compromise added (3)

    Indicators of compromise recorded

  2. 08:09 UTC

    Observed by Previdian sensors

    Evidence-backed exploitation signal

  3. 15:39 UTC

    CVE published

    Vulnerability disclosed publicly

  4. 19:54 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

View Pro pricing Read API docs
  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2026-69255

Free JSON includes basic KEV fields 
{
  "cve_id": "CVE-2026-69255",
  "confidence": "Confirmed",
  "cvss_score": 9.2,
  "cvss_estimated": false,
  "epss_score": 0.00602,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": true
  },
  "sensor_telemetry": { "attempts": 2, "sensors": 1 }
}