Flowise allows arbitrary file write to RCE

Exploitation

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

CVSS 4.0

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

EPSS

• CVE-2025-71338: 1.16% estimated exploitation activity in the next 30 days; percentile 67.10 (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.

Summary An attacker could write files with arbitrary content to the filesystem via the `/api/v1/document-store/loader/process` API. An attacker can reach RCE(Remote Code Execution) via file writing.

Details All file writing functions in packages/components/src/storageUtils.ts are vulnerable. - addBase64FilesToStorage - addArrayFilesToStorage - addSingleFileToStorage The fileName parameter, which is an untrusted external input, is being used as an argument to path.join() without verification. ```javascript const filePath = path.join(dir, fileName) fs.writeFileSync(filePath, bf) ``` Therefore, users can move to the parent folder via `../` and write files to any path. Once file writing is possible in all paths, an attacker can reach RCE (Remote Code Execution) in a variety of ways. In PoC (Proof of Concept), RCE was reached by overwriting package.json.

PoC In PoC, `package.json` is…

Published by the source

14 Mar 2025, 18:48 UTC

Last modified by the source

3 Nov 2026, 17:45 UTC

Source last checked

4 Nov 2026, 06:10 UTC

1. Revision 4 · amended · 4 Nov 2026

   Amended from osv record GHSA-8vvx-qvq9-5948

2. Revision 3 · amended · 3 Nov 2026

   Amended from ghsa record GHSA-8vvx-qvq9-5948

3. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-8vvx-qvq9-5948

4. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-8vvx-qvq9-5948

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

# Patch Next advisory brief: CVE-2025-71338

Advisory: Flowise allows arbitrary file write to RCE
IDs: CVE-2025-71338, GHSA-8vvx-qvq9-5948
Record: https://patchnext.com/advisories/cve-2025-71338 (revision 4, source checked 4 Nov 2026, 06:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm flowise: affected <= 2.2.7

## 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
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## 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-8vvx-qvq9-5948 (OSV record GHSA-8vvx-qvq9-5948 lists affected ranges: npm flowise >=0 <=2.2.7)
- Verified: https://github.com/advisories/GHSA-8vvx-qvq9-5948 (GitHub-reviewed advisory GHSA-8vvx-qvq9-5948 lists affected ranges: npm flowise >=0 <=2.2.7)

Commands are suggestions: review each one before running it.