Flowise: Flowise RCE via SQLite Record Manager Node
Flowise
More for Flowise RSS feed for Flowise
- Severity
- High, CVSS 8.8
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Record
- CVE-2026-69259
- Affects
- Flowise
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- August 4, 2026
- Source last modified
- October 24, 2026
Description
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, the SQLite Record Manager node in packages/components/nodes/recordmanager/SQLiteRecordManager/SQLiteRecordManager.ts accepted user-controlled additionalConfig and spread it after the intended database setting, allowing additionalConfig.database to overwrite the SQLite database path. An authenticated attacker using the published Docker image, which ran as root, could write a SQLite database to paths such as /etc/chromium/exploit.conf; by controlling the table name and namespace value, the attacker could place shell syntax into the database file and trigger execution when Puppeteer launched Chromium and sourced /etc/chromium/*.conf. This issue is fixed in version 3.1.3.
Description quoted from the NVD record.
Who is affected
Flowise is a tool for building apps that use AI language models by dragging and dropping building blocks. This flaw affects versions before 3.1.3 and sits in the SQLite Record Manager building block. Someone who can already log in to Flowise could misuse this block to write a file to a location of their choosing. When Flowise runs from the official ready-made container package (a Docker image), which runs with full administrator rights, the attacker could use this to run their own commands on the server. This flaw is rated High.
What to do
- The person who installed or runs Flowise for your organization should check which version is in use. Any version before 3.1.3 has this flaw.
- Update Flowise to version
3.1.3, which fixes this flaw. This matters most if you run Flowise from the official ready-made container package, because that setup lets an attacker take control of the server. - If an IT provider or vendor runs Flowise for your organization, send them this advisory and ask when the update to version
3.1.3will be done.
Analysis written from the source record as of October 24, 2026 and reviewed before publishing.