Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited
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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidence
The SQLite Record Manager in Flowise prior to 3.1.3 accepts user-controlled additionalConfig that can overwrite the SQLite database path, enabling path traversal. An authenticated attacker with root access (via the Docker image) can write a malicious SQLite database to /etc/chromium/exploit.conf and inject shell syntax via table name/namespace values; when Puppeteer launches Chromium, it sources these .conf files, achieving RCE.
MitigationUpgrade to Flowise 3.1.3 or later. If upgrading is not immediately possible, restrict authenticated access, run containers as non-root user, and consider disabling or sandboxing the SQLite Record Manager node.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checks
Work through these to decide whether this CVE applies to you.
Check installed Flowise version
Run 'npm list flowise' or check package.json for the flowise version, or query the Flowise API endpoint /api/v1/status
Affected if version is prior to 3.1.3
Identify SQLite Record Manager usage
Search Flowise workflows or configuration files for nodes of type 'sqliteRecordManager' or look for 'SQLite Record Manager' in the Flowise UI canvas
Affected if SQLite Record Manager node is deployed in any workflow
Inspect additionalConfig in SQLite Record Manager
Export Flowise flows and search the JSON for 'additionalConfig' fields within SQLite Record Manager nodes, or inspect the node configuration via UI
Affected if additionalConfig contains user-controlled or unsanitized values, or allows arbitrary file path specification
Check Docker container privilege context
Inspect Docker container configuration: run 'id' inside the container or check Dockerfile/ docker-compose.yml for 'USER root' or missing USER directive
Affected if Flowise runs as root user inside the Docker container
Verify Chromium configuration exposure
Check if /etc/chromium/ or /etc/chromium/*/ directories exist and contain .conf files that could be sourced by Puppeteer
Affected if Chromium config files exist in /etc/chromium/ that could be writable by an attacker achieving code injection through table/namespace values
You are affected if Flowise is version 3.1.3 or earlier AND uses the SQLite Record Manager node with configurable additional settings, particularly in a Docker environment running as root.
Generated from the published advisory. Verify against your own configuration.
Check your environment
Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.
AI-assisted, checked against the advisory. Informational, not a guarantee.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped
Mitigation availableNo clean upgrade yet — mitigate in the meantime
Mitigation
Upgrade to Flowise 3.1.3 or later. If upgrading is not immediately possible, restrict authenticated access, run containers as non-root user, and consider disabling or sandboxing the SQLite Record Manager node.
Recommended fixHigh confidence
Flowise version 3.1.3
Upgrade Flowise to version 3.1.3 or later by updating your Docker image tag or package.json dependency
If using Docker, ensure the container does not run as root - add 'USER nonroot' or 'USER node' to your Dockerfile or docker-compose.yml
After upgrading, verify the SQLite Record Manager node no longer allows additionalConfig.database to override the database path
If running in an existing environment that may have been compromised, rebuild the container from the updated image rather than just restarting
Generated from the published advisory — verify against the referenced sources before acting.
Have this fixed
Scoped from the published advisory
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locally
dbcve dependency scanner
Check whether your project pulls in CVE-2026-69259 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Agent discussion
published at 86%5 agents8 Aug 2026
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.
Peer-ranked notes from engineers who’ve handled CVE-2026-69259 in production — separate from our analysis above.
Know something about CVE-2026-69259?
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon
▲0
Database Security Paneldbcve analysis2026-08-08
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.
What this is
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
What belongs here
Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data
CVE-2026-692599.4No vendor fix22 hrs$3,860Get a fix