Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-69258 critical CVSS 9.1

Vulnerability in flowise (CVE-2026-69258)

Summary

Vulnerability in flowise (CVE-2026-69258). Confidential information can be exposed externally. Exploitable via POST /api/v1/prediction/. Mitigation: upgrade to 3.1.3 or later.

Original description

The description as published by the source.

Summary

The POST /api/v1/prediction/:id endpoint — which is unauthenticated (whitelisted in WHITELIST_URLS) — accepts an overrideConfig object in the request body. This object is unconditionally spread into the internal flowConfig and flowData objects at two locations in the codebase without checking apiOverrideStatus. This allows an unauthenticated attacker to inject arbitrary properties into the flow execution context of any public chatflow, enabling session hijacking, cross-session data pollution, chat history manipulation, and injection of attacker-controlled values into $flow.* template variables consumed by flow nodes.

This is distinct from the previously reported overrideConfig vulnerability (GHSA-5cph-wvm9-45gj), which addressed overrideConfig's ability to modify node input parameters via replaceInputsWithConfig(). That function is properly gated behind apiOverrideStatus. The vulnerability reported here is in two separate, ungated spread operations that were not addressed by the GHSA-5cph fix.

Root Cause

In packages/server/src/utils/buildChatflow.ts at lines 557–564, the incomingInput.overrideConfig object is spread directly into flowConfig with no gating:

// File: packages/server/src/utils/buildChatflow.ts, lines 557-564
const flowConfig: IFlowConfig = {
    chatflowid,
    chatflowId: chatflow.id,
    chatId,
    sessionId,
    chatHistory,
    apiMessageId,
    ...incomingInput.overrideConfig  // <-…

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

CVE-2026-69258 (flowise) — CWE-639 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/v1/prediction/ / GET /api/v1/public-chatflows / WHITELIST_URLS / overrideConfig
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-639) 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/ / GET /api/v1/public-chatflows / WHITELIST_URLS / overrideConfig.

🔥 Severity

Severity: Critical (CVSS 9.1/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 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

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