Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-46475 high CVSS 8.8

Vulnerability in flowise (CVE-2026-46475)

Summary

vulnerability in flowise (CVE-2026-46475). Successful exploitation can lead to full system takeover. Exploitable via `PUT /api/v1/assistants/`. Mitigation: upgrade to `3.1.2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-46475** has been found in flowise. Attackers can target a specific entry point like `PUT /api/v1/assistants/` over the network to misuse the product. Successful exploitation can lead to full system takeover. CVSS score: 8.8/10. What to do: upgrade flowise to **3.1.2** or later. If unsure, ask your IT team or search "flowise CVE-2026-46475" on the vendor's site.
CVE-2026-46475 (flowise) — CWE-915 / CVSS v3 8.8 Attack vector: remote (network-reachable) / no user interaction Attack surface: PUT /api/v1/assistants/ / `workspaceId` / `createdDate` / `updatedDate` Patched: `3.1.2` — 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
**A vulnerability** (CWE-915) exists in flowise. Attackers reach the vulnerable code path via `PUT /api/v1/assistants/` without authentication.
📍 Affected scope
flowise — . Attack surface: PUT /api/v1/assistants/ / `workspaceId` / `createdDate` / `updatedDate`.
🔥 Severity
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **3.1.2**.
🛡️ 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 `PUT /api/v1/assistants/` 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 (7 steps)

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. 3
    Hunt for indicators of compromise detect 
    grep 'PUT /api/v1/assistants/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

  3. 6
    Apply patch patch 
    Upgrade flowise to 3.1.2

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

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

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

Affected packages

npm flowise
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.1.2"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →