Code Injection in flowise (CVE-2026-70477)
Summary
Code injection in flowise (CVE-2026-70477). Successful exploitation can lead to full system takeover. Exploitable via run. Mitigation: upgrade to 3.1.3 or later.
Original description
The description as published by the source.
-- ABSTRACT -------------------------------------
Trend Micro's Zero Day Initiative has identified a vulnerability affecting the following products:
Flowise - Flowise
-- VULNERABILITY DETAILS ------------------------
- Version tested: 3.1.1
- Installer file: https://github.com/FlowiseAI/Flowise (npm install flowise@3.1.1)
- Platform tested: Ubuntu 25.10
A prompt injection sent to a chatflow using a CSV Agent node can cause the LLM to respond with a malicious Python script that bypasses the blocklist validator and executes in an unsandboxed pyodide environment. An attacker can leverage this to execute arbitrary code in the context of the user running the server.
This vulnerability allows remote attackers to execute arbitrary code on affected installations of Flowise. Authentication is not required to exploit this vulnerability.
The specific flaw exists within the run method of the CSV_Agents class. The issue results from insufficient input sanitization when using untrusted data to construct an LLM prompt. An attacker can leverage this vulnerability to execute code in the context of the service account.
Analysis
When a user makes a query against a chatflow using the CSV Agent node, the run method of the CSV_Agents class is called. This method reads the CSV file, loads a pyodide environment, and uses pandas to extract column names and data types into a dictionary. It then constructs a system prompt using that dictionary and the user's input, and sends…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-70477 has been found in flowise.
Attackers can target a specific entry point like run over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade flowise to 3.1.3 or later.
If unsure, ask your IT team or search "flowise CVE-2026-70477" on the vendor's site.
CVE-2026-70477 (flowise) — CWE-94 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: run / CSV_Agents / pythonCode / validatePythonCodeForDataFrame
Patched: 3.1.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in flowise. Attackers reach the vulnerable code path via run without authentication.
Check the vendor advisory for the affected versions of flowise. Attack surface: run / CSV_Agents / pythonCode / validatePythonCodeForDataFrame.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 3.1.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'flowise' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'flowise' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
flowiseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade flowise to 3.1.3ステージング環境で 3.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com