Live › vulnerability › GHSA-w5r9-j49j-2m55
Flowise accepts path-traversal values as chatflow and chat IDs, so file handling reads and writes outside its storage folder. An unauthenticated attacker can read arbitrary files and write files, which may lead to remote code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 17:36 UTC. All times on this page are UTC.
Flowise servers at version 2.2.8 or earlier are exposed, since the flaw is in the unauthenticated file endpoints that take a chatflow ID. Teams running Flowise only on a private network with no inbound access from outside have lower exposure. Teams on 3.0.6 or later are not affected.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| flowise | npm | >= 2.2.8, < 3.0.6 | 3.0.6 |
npm ls flowise and see whether it is 2.2.8 or earlier/api/v1/chatflows and endpoints/api/v1/get-upload-file3.0.6 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
This advisory has been withdrawn because it is a duplicate of GHSA-q67q-549q-p849. This link is maintained to preserve external references.
Flowise before 3.0.6 (affected versions 2.2.8 and earlier) contains an arbitrary file access vulnerability due to missing validation that the chatflowId and chatId parameters are UUIDs or numbers in file handling operations. By supplying a path-traversal value (e.g., '../../../../../tmp') as the chatflow id, an unauthenticated attacker can use the /api/v1/chatflows endpoint (via addBase64FilesToStorage) to write arbitrary files, and the /api/v1/get-upload-file and /api/v1/openai-assistants-file/download endpoints (via streamStorageFile) to read arbitrary files. Arbitrary file write may lead to remote code execution.
This page as .md · .json · in your agent: get_signal("GHSA-w5r9-j49j-2m55")
GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.