Flowise: Authenticated Command Execution and Sandbox Bypass via Puppeteer and Playwright Packages

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.4 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:L/SC:H/SI:H/SA:L · score source

EPSS

• CVE-2025-34267: 6.88% estimated exploitation activity in the next 30 days; percentile 94.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. NOTE: This vulnerability was incorrectly assigned as a duplicate CVE-2025-26319 and should be considered distinct from that identifier.

Published by the source

14 Oct 2025, 21:30 UTC

Last modified by the source

29 Oct 2025, 05:14 UTC

Source last checked

25 Oct 2026, 00:12 UTC

1. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-r4hh-pcgx-j5r2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-34267

Advisory: Flowise: Authenticated Command Execution and Sandbox Bypass via Puppeteer and Playwright Packages
IDs: CVE-2025-34267, GHSA-r4hh-pcgx-j5r2
Record: https://patchnext.com/advisories/cve-2025-34267 (revision 2, source checked 25 Oct 2026, 00:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: flowise 3.0.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm flowise: affected >= 3.0.1, < 3.0.8; fixed in 3.0.8

## Suggested inspection (read-only)
- `npm ls flowise --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on flowise.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-r4hh-pcgx-j5r2 (OSV record GHSA-r4hh-pcgx-j5r2 lists affected ranges: npm flowise >=3.0.1 <3.0.8 (fixed))

Commands are suggestions: review each one before running it.