Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-70473 high CVSS 8.5

Information Disclosure in flowise (CVE-2026-70473)

Summary

Vulnerability in flowise (CVE-2026-70473). Confidential information can be exposed externally. Exploitable via GET /api/v1/upsert-history. Mitigation: upgrade to 3.1.3 or later.

Original description

The description as published by the source.

Summary

The GET /api/v1/upsert-history endpoint returns the entire server-wide upsert history (response size >100MB) instead of being scoped to the requesting user/tenant/workspace. The response includes sensitive configuration data (e.g., Vector Store settings such as Qdrant Server URL and collection name), resulting in a High severity information disclosure that may enable further targeted attacks.

Details

  • Affected endpoint: GET /api/v1/upsert-history
  • Observed behavior: The API returns global upsert history for the whole server, indicating missing/insufficient:
    • Authorization checks (RBAC/user-based access control)
    • Data scoping (workspace/project/tenant isolation)
    • Pagination/limits (excessive data exposure and very large responses)
  • Sensitive data exposure: The returned history contains integration parameters and infrastructure details. Example excerpt from the response: 
    {
  "label": "Qdrant",
  "name": "qdrant",
  "category": "Vector Stores",
  "id": "qdrant_0",
  "paramValues": [
    {
      "label": "Qdrant Server URL",
      "name": "qdrantServerUrl",
      "type": "string",
      "value": "https://7f60f255-f7fd-4a1c-a734-fbcf904f9f85.europe-west3-0.gcp.cloud.qdrant.io"
    },
    {
      "label": "Qdrant Collection Name",
      "name": "qdrantCollection",
      "type": "string",
      "value": "fair-herring-azure"
    },
    {
      "label": "Vecto…

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-70473 has been found in flowise.
Attackers can target a specific entry point like GET /api/v1/upsert-history over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.5/10.
What to do: upgrade flowise to 3.1.3 or later.
If unsure, ask your IT team or search "flowise CVE-2026-70473" on the vendor's site.

CVE-2026-70473 (flowise) — CWE-200 / CVSS v3 8.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/upsert-history / GET /api/v1/upsert-history / curl
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

Information disclosure (CWE-200) exists in flowise. Attackers reach the vulnerable code path via GET /api/v1/upsert-history.

📍 Affected scope

Check the vendor advisory for the affected versions of flowise. Attack surface: GET /api/v1/upsert-history / GET /api/v1/upsert-history / curl.

🔥 Severity

Severity: High (CVSS 8.5/10). Confidential information can be exposed externally.

🔧 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/upsert-history 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/upsert-history' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/v1/upsert-history への異常なリクエスト (不正な認証ヘッダ・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/upsert-history 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