CVE-2026-41137: Flowise: Code Injection in CSVAgent leads to Authenticated RCE

Should you act?

Critical, preconditions apply

Severe if exploited, but exploitation needs conditions that may not apply to you. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
• EPSS 2.1%, percentile 81: FIRST’s model estimates a 2.1% chance of exploitation activity in the next 30 days, higher than 81% of all scored CVEs (elevated). EPSS is a probability, not a verdict.
• Needs an account (low (any account)). Exposure depends on who can log in.
• Only applies if your dependency tree includes flowise (npm) <= 3.0.13, fixed in 3.1.0; flowise-components (npm) <= 3.0.13, fixed in 3.1.0. Check your lockfile, including transitive dependencies.

What it is

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, The CSVAgent allows providing a custom Pandas CSV read code. Due to lack of sanitization, an attacker can provide a command injection payload that will get interpolated and executed by the server. This vulnerability is fixed in 3.1.0.

From the GitHub advisory

Summary The CSVAgent allows providing a custom Pandas CSV read code. Due to lack of sanitization, an attacker can provide the following payload: DataFrame({'foo': ['bar!']});import os;os.system('whoami') that will get interpolated and executed by the server.

Details The code in question that introduces the issue is in CSVAgent.ts. customReadCSVFunc is user-controlled and gets interpolated directly without sanitization into the code variable which gets executed by pyodide one line later in: dataframeColDict = await pyodide.runPythonAsync(code). An authenticated attacker can issue the following chain of requests:

1. Create a new chat flow by sending a POST request to /api/v1/chatflows. This will return the chatflowId in the response. 2. Send a POST request to /api/v1/prediction/[CHATFLOWID] to trigger the execution of the chatflow. NOTE: the chatflow can contain only this node in order for the exploit to work. 3. Optionally: send a DELETE request to /api/v1/chatflows to cleanup and delete the chat flow.

Since /chatflows is not whitelisted here, this mandates the user to be authenticated. But, if FLOWISEUSERNAME and FLOWISEPQSSWORD aren't set, it's sufficient to provide the "x-request-from": "internal" header to bypass authentication.

PoC Here's the PoC code:

Weakness type: CWE-94.

Product: flowise (npm) · Assigned by: GitHub_M · Published: 2026-04-23

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Attack requirements: none
• Privileges required: low (any account)
• User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation poc, automatable no, technical impact total.
• FIRST EPSS (model of 2026-10-21): 2.05% probability of exploitation activity in the next 30 days; percentile 81.

Timeline

• 2026-04-16 — GitHub-reviewed advisory GHSA-9wc7-mj3f-74xv published (critical)
• 2026-04-23 — CVE record last updated
• 2026-04-23 — CVE record published by GitHub_M

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-9wc7-mj3f-74xv github.com
2. CVE.org record CVE-2026-41137 cve.org
3. NVD entry CVE-2026-41137 nvd.nist.gov

Other references from the CVE record and advisory

1. github.com github.com

Critical npm advisories · Today’s Security Digest