CVE-2025-34267: Flowise Authenticated Command Execution and Sandbox Bypass via Puppeteer & Playwright Packages
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.
Security readout for executives and security teams
Plain-English summary
A logged-in Flowise user may be able to break out of Flowise's tool execution sandbox and run code on the host server when Puppeteer or Playwright are available through built-in dependencies. This is serious for shared or internet-facing Flowise instances because compromise can move from an application account to the underlying host.
Executive priority
Treat as high priority where Flowise is multi-user, externally reachable, or used near sensitive systems. The main business risk is server compromise from a privileged application account, not unauthenticated internet-wide exploitation.
Technical view
The issue is an authenticated command execution and nodevm sandbox bypass in Flowise involving Puppeteer and Playwright module use. An attacker with high privileges who can create or run a tool can control browser binary paths or parameters, causing host-level execution outside the intended sandbox. The CVSS v4.0 score is 8.4.
Likely exposure
Exposure is most likely in Flowise v3.0.1 through versions before 3.0.8, and later configurations where ALLOW_BUILTIN_DEP is enabled. Risk depends on whether authenticated users can create or execute tools using Puppeteer or Playwright.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires authentication with sufficient privileges, but no user interaction and low attack complexity are indicated.
Researcher notes
CVE-2025-34267 is described as distinct from CVE-2025-26319 despite developer duplicate handling. The affected-version evidence is partly inconsistent: the record lists Flowise 3.0.1, while the description states pre-3.0.8 and later ALLOW_BUILTIN_DEP-enabled configurations.
Mitigation direction
Check the Flowise advisory for the currently recommended fixed version or configuration change.
Disable ALLOW_BUILTIN_DEP where not required by business workflows.
Restrict tool creation and execution to trusted administrators only.
Review whether Puppeteer or Playwright are exposed inside Flowise tool execution.
Isolate Flowise hosts and limit sensitive host permissions.
Validation and detection
Inventory Flowise versions and flag 3.0.1 through pre-3.0.8 deployments.
Check runtime configuration for ALLOW_BUILTIN_DEP enabled.
Review Flowise users who can create or run tools.
Look for workflows using Puppeteer or Playwright modules.
Review host logs for unexpected child process or browser binary execution.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-77: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-77 · source CWE mapping
Improper Neutralization of Special Elements used in a Command ('Command Injection')
Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.