dbcve.org
FlowiseApplication · Flowiseai

CVE-2025-34267

CRITICAL · 9.9 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 3.0.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Flowise v3.0.1 < 3.0.8 and all versions after with 'ALLOW_BUILTIN_DEP' enabled contain an authenticated remote code execution vulnerability and node VM sandbox escape due to insecure use of integrated modules (Puppeteer and Playwright) within the nodevm execution environment. An authenticated attacker able to create or run a tool that leverages Puppeteer/Playwright can specify attacker-controlled browser binary paths and parameters. When the tool executes, the attacker-controlled executable/parameters are run on the host and circumvent the intended nodevm sandbox restrictions, resulting in execution of arbitrary code in the context of the host. This vulnerability was incorrectly assigned as a duplicate CVE-2025-26319 by the developers and should be considered distinct from that identifier.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Flowise versions 3.0.1 through <3.0.8 with ALLOW_BUILTIN_DEP enabled allows authenticated attackers to achieve RCE by specifying attacker-controlled browser binary paths when using Puppeteer/Playwright integrated modules within the nodevm sandbox, bypassing intended sandbox restrictions.

MitigationUpgrade to Flowise v3.0.8 or later which addresses the sandbox escape. If upgrading is not immediately possible, disable ALLOW_BUILTIN_DEP and implement strict allow-listing of executable paths for browser automation features.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FlowiseApplication
Affected:>= 3.0.1, < 3.0.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Flowise version
    Run 'npm list flowise' or check the package.json file in your Flowise installation directory to determine the exact version number.
    Affected if Version is 3.0.1 through 3.0.7 (versions below 3.0.1 are not affected, 3.0.8 and later contain the fix)
  2. Locate Flowise configuration file
    Find the Flowise configuration file where runtime environment variables are stored - typically an .env file or config file in the Flowise installation directory.
    Affected if Configuration file exists and can be inspected for runtime settings
  3. Verify ALLOW_BUILTIN_DEP setting
    In the configuration file, search for the ALLOW_BUILTIN_DEP parameter and confirm whether it is set to 'true' or '1' (enabled).
    Affected if ALLOW_BUILTIN_DEP is explicitly enabled (set to true, 1, or yes)
  4. Check for Puppeteer or Playwright tool usage
    Review your Flowise chatflow configurations or tool definitions for any tools that utilize Puppeteer or Playwright integrations - these are the attack vectors for this vulnerability.
    Affected if Any chatflows or tools are configured to use Puppeteer or Playwright integrated tools

You are affected if your Flowise version is 3.0.1-3.0.7 AND ALLOW_BUILTIN_DEP is enabled AND you have Puppeteer/Playwright tools configured in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.0.8 or later
Fixed in 3.0.8
Vendor patch github.com →
Interim mitigation

Upgrade to Flowise v3.0.8 or later which addresses the sandbox escape. If upgrading is not immediately possible, disable ALLOW_BUILTIN_DEP and implement strict allow-listing of executable paths for browser automation features.

Recommended fix High confidence

Flowise 3.0.8

  1. Upgrade Flowise to version 3.0.8 or later to address the command injection vulnerability
  2. After upgrading, verify that the ALLOW_BUILTIN_DEP configuration setting is properly secured according to your security requirements
  3. If immediate upgrade is not possible, disable the ALLOW_BUILTIN_DEP configuration flag as a temporary mitigation to reduce the attack surface

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Flowise Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34267 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-34267 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data