Is CVE-2025-34267 exploited in the wild?

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

How severe is CVE-2025-34267?

Critical severity, with a CVSS score of 9.9, published 14 October 2025.

Which products and versions are affected?

flowise (npm) SEMVER:introduced=3.0.1,fixed=3.0.8.

Is there a fix for CVE-2025-34267?

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

How is CVE-2025-34267 attacked?

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

Am I affected by CVE-2025-34267?

Check whether you run flowise (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-2025-34267: Flowise remote code execution via Puppeteer and Playwright sandbox escape

CVE-2025-34267 · Severity: critical · CVSS 9.9 · Published 2025-10-14

Flowise, an open-source platform for building AI agents and workflows, contains a vulnerability that allows authenticated users to execute arbitrary commands on the underlying server. By creating a custom tool that uses built-in browser automation modules, an attacker can bypass security restrictions to run malicious code. This could lead to a complete takeover of the server, theft of sensitive AI training data, or disruption of automated business workflows.

Technologies: flowise (npm). Vendors: npm.

Quick answers

Is CVE-2025-34267 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-34267 being exploited in the wild.
How severe is CVE-2025-34267?: Critical severity, with a CVSS score of 9.9, published 14 October 2025.
Which products and versions are affected?: flowise (npm) SEMVER:introduced=3.0.1,fixed=3.0.8.
Is there a fix for CVE-2025-34267?: Yes. flowise (npm): upgrade to 3.0.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-34267 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2025-34267?: Check whether you run flowise (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.0.8 or later
```
npm install flowise@3.0.8
```

Technical details

Flowise versions 3.0.1 through 3.0.8 (and later versions where 'ALLOW_BUILTIN_DEP' is enabled) are vulnerable to a sandbox escape in the NodeVM execution environment. The vulnerability stems from the insecure integration of Puppeteer and Playwright modules, which allow users to specify attacker-controlled browser binary paths and command-line arguments. An authenticated attacker can create a custom tool that leverages these modules to execute arbitrary binaries on the host system, bypassing the intended NodeVM sandbox. The exploit is triggered by sending a crafted JSON object to the /api/v1/tools endpoint and executing the resulting tool via an Agentflow or Chatflow. The issue was addressed by disabling available dependencies by default in version 3.0.8.

Affected products

FlowiseAI FlowiseAI Flowise 3.0.1 to 3.0.8; all versions after 3.0.8 if ALLOW_BUILTIN_DEP is enabled

Identifiers

CVE-2025-34267
GHSA-r4hh-pcgx-j5r2

Timeline

2025-09-18: patched: Pull request merged to disable dependencies by default
2025-10-03: advisory: Vendor advisory GHSA-5w3r-f6gm-c25w published
2025-10-14: disclosed: CVE-2025-34267 published to NVD

References

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