Vulnerability report

Active exploitation observed Confirmed confidence Not in CISA KEV

CVE-2026-46442

Flowise Remote Code Execution

FlowiseAI / Flowise · affected before 3.1.2

Severity
CVSS 9.4 · Critical
Confidence
Confirmed
Exploit status
Observed in sensors
EPSS
3.5%
First observed
13 Jul 2026
Last observed
17 Aug 2026

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2026-46442 is a vulnerability affecting FlowiseAI Flowise. Flowise is a drag & drop user interface to build a customized large language model flow. Prior to version 3.1.2, POST /api/v1/node-custom-function lacks...

Is it exploited?

Yes. KEV Intelligence sensors observed exploitation attempts with confirmed confidence.

Who is affected?

FlowiseAI / Flowise affected before 3.1.2.

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 version 3.1.2, POST /api/v1/node-custom-function lacks route-level authorization, allowing any authenticated user or API key to submit arbitrary JavaScript to the Custom JS Function node. When E2B_APIKEY is not configured — the common deployment case — Flowise executes this code inside a NodeVM sandbox.

This sandbox can be escaped, allowing an attacker to reach the host process object and execute system commands via child_process. The result is authenticated remote code execution on the Flowise server host. This issue has been patched in version 3.1.2.

Vendor Product Affected Status
FlowiseAI Flowise Before 3.1.2 Affected
Published
08 Jun 2026
Exploitation Reported
13 Jul 2026
Attack vector
Remote
Complexity
Low
Privileges
Low
User interaction
None

Tags

nuclei_scanner

CVE References

Exploitation evidence

Why KEV Intelligence 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

KEV Intelligence

Recorded 13 Jul 2026

Independent exploitation attestation added to the KEV Intelligence record.

Active exploitation observed

KEV Intelligence sensor

First observed 13 Jul 2026

First-party sensor telemetry confirms matching exploitation attempts.

Proof of concept available

GitHub

Recorded 17 Jul 2026

Public scanner or PoC coverage increases practical exploitability.

Known exploited vulnerability sources

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

Learn about Pro API access
Source Added
KEV Intelligence First 2026-07-17 07:51 UTC

Operational indicators for this CVE are listed under Detection.

Sensor telemetry

First-party evidence of exploitation activity

Aggregate observations show the scale, recency, and distribution of activity without overstating sparse data.

30

Attempts observed

14

Unique attacker IPs

9

Attacker countries

AF · AT · CN · DE · IN · JP · NL · RO · US

1

Sensors observed

Exploitation attempts over the last 39 days

Daily events observed by KEV Intelligence sensors

Updated 19 Aug 2026

0
4
0
0
3
15
14
1
6
7
0
0
2
0
0
0
2
3
0
0
2
3
0
0
0
0
0
0
0
0
0
1
3
0
0
0
7
0
0
12 Jul 20 Jul 28 Jul 5 Aug 19 Aug

First observed 13 Jul 2026 · Last observed 17 Aug 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
1
User-Agents
27

Raw values available in Pro and Enterprise.

Virtual patch status

No KEV Intelligence 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

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Risk and context

Severity, weaknesses, and research context

CVSS v4.0

9.4 Critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

EPSS

3.5%

Recent mention · Github Advisory Database (NPM)

[flowise-components] Flowise: CSV Agent Remote Code Execution via Pyodide Code Injection — Root Shell Verified

UPDATE 2026-05-20: Full RCE as root VERIFIED This is not theoretical — a Meterpreter reverse shell session as root has been established on Flowise 3.1.2. Verified Exploit Chain Python code injection via base64_string = "${base64String}" (CSVAgent.ts line 161) Pyodide js...

Read full advisory

All CVSS Scores

CVSS v4.0 9.4 Critical

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

CVSS v3.1 9.9 Critical

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

All Mentions

Recent mention · Github Advisory Database (NPM)

[flowise-components] Flowise: CSV Agent Remote Code Execution via Pyodide Code Injection — Root Shell Verified

Github Advisory Database (NPM) · 04 Aug 2026

UPDATE 2026-05-20: Full RCE as root VERIFIED This is not theoretical — a Meterpreter reverse shell session as root has been established on Flowise 3.1.2. Verified Exploit Chain Python code injection via base64_string = "${base64String}" (CSVAgent.ts line 161) Pyodide js bridge provides access to the host Node.js process process.mainModule.constructor._load('child_process') loads child_process (bypasses ESM require restriction) .execSync('CMD') executes arbitrary OS commands as root (PID 1 in container) Working RCE Payload ";import...

Recent mention · Github Advisory Database (NPM)

[flowise] Flowise: CSV Agent Remote Code Execution via Pyodide Code Injection — Root Shell Verified

Github Advisory Database (NPM) · 04 Aug 2026

UPDATE 2026-05-20: Full RCE as root VERIFIED This is not theoretical — a Meterpreter reverse shell session as root has been established on Flowise 3.1.2. Verified Exploit Chain Python code injection via base64_string = "${base64String}" (CSVAgent.ts line 161) Pyodide js bridge provides access to the host Node.js process process.mainModule.constructor._load('child_process') loads child_process (bypasses ESM require restriction) .execSync('CMD') executes arbitrary OS commands as root (PID 1 in container) Working RCE Payload ";import...

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

Timeline

From disclosure to observed exploitation

  1. Public PoC available

    Public proof-of-concept code published

  2. Nuclei template available

    Scanner coverage available

  3. Observed by KEV Intelligence sensors

    Evidence-backed exploitation signal

  4. Indicators of compromise added (29)

    Indicators of compromise recorded

  5. CVE published

    Vulnerability disclosed publicly

  6. 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.

  • 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-46442

Free JSON includes basic KEV fields
{
  "cve_id": "CVE-2026-46442",
  "confidence": "Confirmed",
  "cvss_score": 9.4,
  "cvss_estimated": false,
  "epss_score": 0.03489,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": true
  },
  "sensor_telemetry": { "attempts": 30, "sensors": 1 }
}

Early warning alerts

Get alerts on high-impact exploitation

Receive curator-selected alerts when exploitation activity warrants attention. Each alert includes the evidence and context needed to decide what requires attention now.

Occasional high-impact alerts. Unsubscribe anytime. See our Privacy Policy.