CVE-2026-69259

This vulnerability in Flowise's SQLite Record Manager node lets an authenticated user control database file paths through the `additionalConfig` parameter. When this path is written to a location Chromium later parses—specifically `/etc/chromium/*.conf`—the arbitrary text embedded in the SQLite file (which permits shell syntax) becomes executable code. The attack chain is write-anywhere-root-can-write plus wait-for-Chromium-parse, and it works because Flowise's Docker image runs as root by default. The 'authenticated attacker' framing in the CVE description obscures the real issue: Flowise is a development tool frequently deployed with authentication disabled or trivially weak, and more fundamentally, its architecture conflates authentication with authorization. The `additionalConfig` parameter exists because Flowise treats every authenticated user as a trusted flow author with legitimate power over system configuration. That's a structural design failure, not a boundary-calibration problem. The Chromium config-sourcing behavior isn't a one-off interaction—it belongs to the same vulnerability family as `.bashrc` injection, SSH `authorized_keys` placement, and cron job poisoning: write to a file a privileged process will parse. The pattern of user input controlling filesystem locations of subsequent parsing appears in other AI toolchain dependencies and deserves systematic audit. Before upgrading to 3.1.3, verify whether the patch removes the `additionalConfig` override capability entirely, sanitizes the database path parameter, or merely reorders spread priority. The third option leaves the underlying architecture intact. Audit other nodes in your Flowise deployment for similar user-input-to-filesystem patterns—this vulnerability almost certainly isn't isolated to the SQLite Record Manager.

Reviewed through automated stages and approved by a human before publication.