Is CVE-2026-69259 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-69259 being exploited in the wild.

How severe is CVE-2026-69259?

Critical severity, with a CVSS score of 8.8, published 4 August 2026.

Which products and versions are affected?

flowise (npm) <= 3.1.2, SEMVER:introduced=0,fixed=3.1.3; flowise-components (npm) <= 3.1.2, SEMVER:introduced=0,fixed=3.1.3.

Is there a fix for CVE-2026-69259?

Yes. flowise (npm): upgrade to 3.1.3 or later; flowise-components (npm): upgrade to 3.1.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-69259 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-69259?

Check whether you run flowise (npm) or flowise-components (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-69259: Flowise Remote Code Execution in SQLite Record Manager node

Q: Which products and versions are affected?

flowise (npm) <= 3.1.2, SEMVER:introduced=0,fixed=3.1.3; flowise-components (npm) <= 3.1.2, SEMVER:introduced=0,fixed=3.1.3.

Q: Is there a fix for CVE-2026-69259?

Yes. flowise (npm): upgrade to 3.1.3 or later; flowise-components (npm): upgrade to 3.1.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-69259 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-69259?

Check whether you run flowise (npm) or flowise-components (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-69259 · Severity: critical · CVSS 8.8 · Published 2026-08-04

Flowise, a platform for building AI applications, contains a vulnerability in its SQLite Record Manager component. An authenticated user can manipulate database settings to write malicious files to sensitive areas of the server's filesystem. Because the application often runs with high system privileges (root), this allows an attacker to execute arbitrary commands on the underlying server, potentially leading to a full system takeover and theft of sensitive data.

Technologies: flowise (npm), flowise-components (npm). Vendors: npm.

Quick answers

Is CVE-2026-69259 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-69259 being exploited in the wild.
How severe is CVE-2026-69259?: Critical severity, with a CVSS score of 8.8, published 4 August 2026.
Which products and versions are affected?: flowise (npm) <= 3.1.2, SEMVER:introduced=0,fixed=3.1.3; flowise-components (npm) <= 3.1.2, SEMVER:introduced=0,fixed=3.1.3.
Is there a fix for CVE-2026-69259?: Yes. flowise (npm): upgrade to 3.1.3 or later; flowise-components (npm): upgrade to 3.1.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-69259 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-69259?: Check whether you run flowise (npm) or flowise-components (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

flowise (npm): upgrade to 3.1.3 or later
```
npm install flowise@3.1.3
```
flowise-components (npm): upgrade to 3.1.3 or later
```
npm install flowise-components@3.1.3
```

Technical details

A vulnerability in the `SQLiteRecordManager.ts` component of Flowise allows for Remote Code Execution (RCE). The `init` method of the `SQLiteRecordManager_RecordManager` class uses keyword argument expansion (`...additionalConfiguration`) after the default `database` path is set, allowing a user-controlled `additionalConfig` input to overwrite the SQLite database file path. By specifying a path such as `/etc/chromium/exploit.conf` and crafting a malicious SQLite database (leveraging specific table name lengths to bypass regex validation and inject shell commands into the database binary structure), an attacker can achieve code execution when the system later invokes Puppeteer/Chromium. This is particularly impactful as the official Docker images run as the root user. The issue is addressed in version 3.1.3.

Affected products

FlowiseAI flowise <= 3.1.2
FlowiseAI flowise-components <= 3.1.2

Identifiers

CVE-2026-69259
GHSA-x3hf-7cj6-3r4m

Timeline

2026-04-24: disclosed: Initial disclosure by Alex Brown
2026-07-29: advisory
2026-08-04: patched: Updated advisory and patch verification

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.