Code Injection in flowise (CVE-2026-69259)
Summary
Code injection in flowise (CVE-2026-69259). Successful exploitation can lead to full system takeover. Exploitable via additionalConfig. Mitigation: upgrade to 3.1.3 or later.
Original description
The description as published by the source.
=============================================================================
Security Advisory
elttam
Topic: Flowise RCE via SQLite Record Manager Node
Module: FlowiseAI/Flowise
Disclosed: 24-Apr-2026
Credits: Alex Brown
Affects: FlowiseAI/Flowise 3.1.2
I. Background
Flowise AI is an open-source, low-code platform for building AI applications—such as chatbots, workflows, and autonomous agents—through an intuitive drag-and-drop interface, minimising the need for extensive coding.
Flowise allows users to connect to a local SQLite database for record management of Upsert Vector Store operations.
II. Problem Description
The database path for the "SQLite Record Manager" node could be overridden using the additionalConfig input, as demonstrated in the following code snippet.
class SQLiteRecordManager_RecordManager implements INode {
...
async init(nodeData: INodeData, _: string, options: ICommonObject): Promise {
const _tableName = nodeData.inputs?.tableName as string
c…
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-69259 has been found in flowise.
Attackers can target a specific entry point like additionalConfig 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-69259" on the vendor's site.
CVE-2026-69259 (flowise) — CWE-94 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: additionalConfig / additionalConfiguration / database / root
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.
Arbitrary code execution (CWE-94) exists in flowise. Attackers reach the vulnerable code path via additionalConfig.
Check the vendor advisory for the affected versions of flowise. Attack surface: additionalConfig / additionalConfiguration / database / root.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 3.1.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. 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
-
1Identify exposure identify
grep -r 'flowise' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
flowiseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade flowise to 3.1.3ステージング環境で 3.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com