Skip to content
This repository was archived by the owner on Aug 13, 2026. It is now read-only.

Authenticated Sandbox Escape and Data Exfiltration via Pandas Methods Bypass in pythonCodeValidator

High
igor-magun-wd published GHSA-x58f-9m57-qc4m Jul 29, 2026

Package

npm flowise (npm)

Affected versions

<= 3.1.2

Patched versions

3.1.3

Description

Summary

The pythonCodeValidator.ts uses a denylist approach to prevent malicious Python execution inside Pyodide. However, this denylist misses native Pandas DataFrame methods (such as to_csv, to_json, pipe, and query). An authenticated user interacting with the CSVAgent can trick the LLM into generating these allowed Pandas methods, escaping the intended sandbox restrictions to achieve arbitrary data exfiltration and server filesystem writes.

Details

The core vulnerability lies in packages/components/src/pythonCodeValidator.ts. The validator relies on 44 regex patterns to block dangerous strings like eval(), exec(), os., and subprocess..

Because the CSVAgent uses Pandas by default, an attacker can bypass the validator entirely by utilizing Pandas native methods. The validator does not block df.to_csv(), df.to_json(), df.query(), or df.pipe(). Because Pyodide executes whatever passes the validator, an attacker can write arbitrary CSV data to the host filesystem or dump all uploaded data.

PoC

  1. We extracted the exact 44 regex rules from pythonCodeValidator.ts.
  2. We tested the following payloads, and all of them successfully bypass the validator:
# Bypass 1: Writes arbitrary CSV data to the server's filesystem
df.query("Age > 20")["Name"].to_csv("/tmp/exfil_data.csv")

# Bypass 2: Dumps the entire dataset (full exfiltration)
df.to_json()

# Bypass 3: Executes arbitrary expressions inside query
result = df.query("Name == Name")["Age"].sum()

When an attacker prompts the CSVAgent with "Save the results to a file for me", the LLM naturally generates df.to_csv("/tmp/exfil.csv"). This passes the validator and Pyodide executes the file write.

Impact

This is a Sandbox Escape leading to data exfiltration and arbitrary file writes to the host filesystem. Any authenticated user who can interact with a CSVAgent or upload a CSV can extract all dataset records or write files to the server.

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v4 base metrics

Exploitability Metrics
Attack Vector Network
Attack Complexity Low
Attack Requirements None
Privileges Required Low
User interaction None
Vulnerable System Impact Metrics
Confidentiality High
Integrity High
Availability None
Subsequent System Impact Metrics
Confidentiality None
Integrity None
Availability None

CVSS v4 base metrics

Exploitability Metrics
Attack Vector: This metric reflects the context by which vulnerability exploitation is possible. This metric value (and consequently the resulting severity) will be larger the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable system. The assumption is that the number of potential attackers for a vulnerability that could be exploited from across a network is larger than the number of potential attackers that could exploit a vulnerability requiring physical access to a device, and therefore warrants a greater severity.
Attack Complexity: This metric captures measurable actions that must be taken by the attacker to actively evade or circumvent existing built-in security-enhancing conditions in order to obtain a working exploit. These are conditions whose primary purpose is to increase security and/or increase exploit engineering complexity. A vulnerability exploitable without a target-specific variable has a lower complexity than a vulnerability that would require non-trivial customization. This metric is meant to capture security mechanisms utilized by the vulnerable system.
Attack Requirements: This metric captures the prerequisite deployment and execution conditions or variables of the vulnerable system that enable the attack. These differ from security-enhancing techniques/technologies (ref Attack Complexity) as the primary purpose of these conditions is not to explicitly mitigate attacks, but rather, emerge naturally as a consequence of the deployment and execution of the vulnerable system.
Privileges Required: This metric describes the level of privileges an attacker must possess prior to successfully exploiting the vulnerability. The method by which the attacker obtains privileged credentials prior to the attack (e.g., free trial accounts), is outside the scope of this metric. Generally, self-service provisioned accounts do not constitute a privilege requirement if the attacker can grant themselves privileges as part of the attack.
User interaction: This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable system. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner.
Vulnerable System Impact Metrics
Confidentiality: This metric measures the impact to the confidentiality of the information managed by the VULNERABLE SYSTEM due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.
Integrity: This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of the VULNERABLE SYSTEM is impacted when an attacker makes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging).
Availability: This metric measures the impact to the availability of the VULNERABLE SYSTEM resulting from a successfully exploited vulnerability. While the Confidentiality and Integrity impact metrics apply to the loss of confidentiality or integrity of data (e.g., information, files) used by the system, this metric refers to the loss of availability of the impacted system itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system.
Subsequent System Impact Metrics
Confidentiality: This metric measures the impact to the confidentiality of the information managed by the SUBSEQUENT SYSTEM due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.
Integrity: This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of the SUBSEQUENT SYSTEM is impacted when an attacker makes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging).
Availability: This metric measures the impact to the availability of the SUBSEQUENT SYSTEM resulting from a successfully exploited vulnerability. While the Confidentiality and Integrity impact metrics apply to the loss of confidentiality or integrity of data (e.g., information, files) used by the system, this metric refers to the loss of availability of the impacted system itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

CVE ID

CVE-2026-73484

Weaknesses

Incomplete List of Disallowed Inputs

The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete. Learn more on MITRE.

Credits