Loading vulnerability…
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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A remote code execution issue in Flowise caused by user-controlled configuration in the SQLite Record Manager node that lets an authenticated attacker overwrite the SQLite database path and, in the published Docker image running as root, write crafted files to Chromium config paths to achieve code execution when Puppeteer launches Chromium.
A critical Flowise SQLite Record Manager vulnerability that permits an authenticated attacker to overwrite the SQLite database path. In the affected root-running Docker image, this can enable writing attacker-controlled content to Chromium configuration paths and result in code execution when Puppeteer starts Chromium.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.