Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-73487 – Prompt Injection to RCE/SSRF/Data Exfiltration – Flowise and flowise-components < 3

Be the first to know when new zero-days emerge:

Summary

CVE-2026-73487 is a code-injection vulnerability (CWE-94) in Flowise, an open-source generative AI development platform, affecting the CSV Agent and Airtable Agent nodes. The regex-based Python code validator used to sanitize LLM-generated code can be bypassed, allowing an unauthenticated attacker to smuggle malicious Python through prompt injection and exfiltrate data, perform SSRF, or execute code. The flaw carries a CVSS score of 9.0 (Critical).

Technical details

  • Root cause: the validatePythonCodeForDataFrame() function relies on a regex-based blocklist (~38 patterns) intended to stop dangerous Python operations before code runs in the CSV/Airtable Agent’s Pyodide execution environment.
  • The blocklist misses multiple bypasses: pandas I/O functions such as pd.read_json(), pd.read_csv(), and pd.read_html() are not blocked and can make outbound HTTP requests; bimportb regex fails to catch importlib; chr() allows dynamic string construction to evade string matching; np.ctypeslib remains available for native library loading.
  • Trigger condition: an attacker sends a crafted prompt to a chatflow that uses the CSV Agent or Airtable Agent node, causing the LLM to generate a malicious Python snippet that the flawed validator lets through.
  • Attack vector: network, via Flowise’s unauthenticated prediction API — no authentication or user interaction is required.
  • Impact: exfiltration of CSV/Airtable datasets to attacker-controlled servers, SSRF against internal services (including cloud metadata endpoints), and potential remote code execution in the Pyodide execution context.

Affected software

  • Flowise (npm package flowise): versions 0 up to (but not including) 3.1.3
  • Flowise components (npm package flowise-components): versions 0 up to (but not including) 3.1.3
  • Fixed in: Flowise 3.1.3

Severity

  • CVSS v4.0 Base Score: 9.0 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N

Mitigation and recommended actions

  • Immediate: upgrade Flowise and flowise-components to version 3.1.3 or later, which addresses the validator bypass.
  • If immediate patching is not possible: disable or restrict access to the CSV Agent and Airtable Agent nodes in chatflows, and restrict/authenticate access to the prediction API endpoints so it is not reachable from untrusted networks.
  • Additionally, isolate any code-execution environments (e.g., Pyodide sandboxes) from sensitive internal networks and cloud metadata services to limit SSRF impact until patched.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Flowise - Build AI Agents, Visually, Flowise - Low-code LLM apps builder
  • author meta tag: FlowiseAI
  • description meta tag: Open source generative AI development platform for building AI agents
  • Raw response body: data-rewardful="9a3a26", og:site_name referencing flowiseai.com

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge