Is CVE-2026-69253 exploited in the wild?

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

How severe is CVE-2026-69253?

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

Which products and versions are affected?

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

Is there a fix for CVE-2026-69253?

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-69253 attacked?

It is attacked over the network.

Am I affected by CVE-2026-69253?

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-69253: Flowise JavaScript sandbox escape to RCE

CVE-2026-69253 · Severity: high · CVSS 8.8 · Published 2026-08-04

Flowise is an open-source low-code platform for building AI applications with drag-and-drop workflows that can execute custom JavaScript code in a sandbox. An attacker with the ability to inject malicious JavaScript into a Custom Function Agent Flow node or Custom Tool can escape the sandbox and gain remote code execution on the server. This allows complete compromise of the server running Flowise and access to any data or systems it can reach.

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

Quick answers

Is CVE-2026-69253 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-69253 being exploited in the wild.
How severe is CVE-2026-69253?: High severity, with a CVSS score of 8.8, published 4 August 2026.
Which products and versions are affected?: flowise (npm) SEMVER:introduced=0,fixed=3.1.3; flowise-components (npm) SEMVER:introduced=0,fixed=3.1.3.
Is there a fix for CVE-2026-69253?: 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-69253 attacked?: It is attacked over the network.
Am I affected by CVE-2026-69253?: 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

The vulnerability is a sandbox escape in Flowise's use of the deprecated vm2 library to isolate custom JavaScript code. The root cause is that vm2 executes code in the same Node.js process, making true isolation impossible. Attackers can bypass the moment library's CVE-2022-24785 path-traversal patch by providing an object with a custom match() function that always returns true, allowing directory traversal. By combining this with the allowed moment dependency, an attacker can load arbitrary files and achieve RCE. The vulnerability requires the ability to inject JavaScript into a Custom Function Agent or Custom Tool node. Flowise has patched this by switching to the E2B sandbox in version 3.1.3, which properly isolates execution in a separate environment.

Affected products

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

Identifiers

CVE-2026-69253
GHSA-wg86-r78f-74mp

Timeline

2026-04-11: disclosed: Vulnerability disclosed by Luke Jahnke and Alex Brown
2026-07-29: advisory: GitHub security advisory GHSA-wg86-r78f-74mp published
2026-08-04: patched: Patch released in version 3.1.3 switching to E2B sandbox

References

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