CVE-2026-69259
Authenticated RCE via SQLiteRecordManager allowing crafted conf write and Chromium execution.
Is CVE-2026-69259 being exploited?
Not confirmed. CVE-2026-69259 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.69% probability of exploitation in the next 30 days.
How severe is CVE-2026-69259?
CVE-2026-69259 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-69259?
Yes. A fix has been recorded for CVE-2026-69259. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-69259 affect?
CVE-2026-69259 affects Flowise < 3.1.3, Flowise Docker image (published runs as root), SQLiteRecordManager node (packages/components/nodes/recordmanager). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-69259?
Upgrade Flowise to >=3.1.3; avoid running Docker as root; inspect and remove /etc/chromium/*.conf; rebuild/redeploy images.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker in Flowise Docker (runs as root) can write files (e.g., /etc/chromium/*.conf) and achieve remote code execution when Chromium/Puppeteer launches.
Immediate action required
- affected< 3.1.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.