Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-70472 high CVSS 8.8

Vulnerability in flowise (CVE-2026-70472)

Summary

Vulnerability in flowise (CVE-2026-70472). Successful exploitation can lead to full system takeover. Exploitable via GET /api/v1/openai-assistants-vector-store. Mitigation: upgrade to 3.1.3 or later.

Original description

The description as published by the source.

Summary

These endpoints accept a client-controlled credential parameter. The server loads credentials by id and uses them directly, without checking whether that credential belongs to the caller’s workspace. If an attacker knows another workspace’s credentialId, they can use that workspace’s OpenAI key.

Details

Route permissions (assistants:*) only check feature access. They do not check credential ownership. The controller passes req.query.credential straight to the service. The service does findOneBy({ id: credentialId }), decrypts the credential, and calls OpenAI APIs. There is no workspaceId check in this flow, so this is an IDOR.

Impact

  • Cross-workspace unauthorized use of stored OpenAI keys.
  • Unauthorized read/modify/delete of victim vector stores and files.
  • Direct billing impact on victim OpenAI account.
  • Multi-tenant boundary violation with practical exploitability.

Reproduction steps

  1. Set up two workspaces: A (attacker) and B (victim), each with an OpenAI credential.
  2. Log in as a user in workspace A (with assistants-related permissions).
  3. Call /api/v1/openai-assistants-vector-store and set credential to B’s credential ID.
  4. Example: GET /api/v1/openai-assistants-vector-store?credential=.
  5. If responses/actions are executed using B’s credential context, the issue is confirmed.

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-70472 has been found in flowise.
Attackers can target a specific entry point like GET /api/v1/openai-assistants-vector-store 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.3 or later.
If unsure, ask your IT team or search "flowise CVE-2026-70472" on the vendor's site.

CVE-2026-70472 (flowise) — CWE-285 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/openai-assistants-vector-store / credential / credentialId / req.query.credential
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

A vulnerability (CWE-285) exists in flowise. Attackers reach the vulnerable code path via GET /api/v1/openai-assistants-vector-store.

📍 Affected scope

Check the vendor advisory for the affected versions of flowise. Attack surface: GET /api/v1/openai-assistants-vector-store / credential / credentialId / req.query.credential.

🔥 Severity

Severity: High (CVSS 8.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 GET /api/v1/openai-assistants-vector-store 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 'GET /api/v1/openai-assistants-vector-store' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/v1/openai-assistants-vector-store への異常なリクエスト (不正な認証ヘッダ・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 GET /api/v1/openai-assistants-vector-store on staging to confirm patch closes the vector

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

Affected packages

npm flowise
[{"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