Loading vulnerability…
Flowise SQLite Record Manager Arbitrary File Write and RCE
CVE-2026-69259 affects Flowise versions before 3.1.3. The SQLite Record Manager node merges user-controlled additional configuration after assigning its intended SQLite database setting, allowing an authenticated user to override the database path. This permits creation of an attacker-controlled SQLite database at an arbitrary writable filesystem location. In the published root-running container, attacker-controlled table-name and namespace values can place shell syntax into a Chromium configuration file; when Puppeteer subsequently launches Chromium, the configuration may be sourced and execute the injected commands. Flowise corrected the issue in version 3.1.3.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
An authenticated attacker can obtain arbitrary file write as the Flowise container user. In affected published Docker deployments, the container runs as root, allowing writes to privileged filesystem locations. By targeting a Chromium configuration file and causing Puppeteer to launch Chromium, the attacker can achieve command execution as root in the container, resulting in complete compromise of the Flowise application and container environment.
If you can’t patch tonight, do this now.
Until updates are deployed, restrict access to Flowise accounts capable of configuring or invoking the SQLite Record Manager node, and prevent untrusted users from supplying its additional configuration, table-name, or namespace inputs. Run Flowise containers as a dedicated non-root user with a read-only root filesystem where practical, restrict write permissions to a dedicated application data directory, and avoid or restrict Puppeteer/Chromium execution.
Patch, then assume compromise.
Upgrade Flowise and flowise-components to version 3.1.3 or later. Ensure the SQLite Record Manager does not allow user-supplied additional configuration to override the database path.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.