Flowise: Flowise before 3.0.6 (affected versions 2.2.8 and earlier) contains an arbitrary file access…
Flowise
More for Flowise RSS feed for Flowise
- Severity
- Critical, CVSS 9.8
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Record
- CVE-2025-71334
- Affects
- Flowise
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- June 25, 2026
- Source last modified
- October 12, 2026
Description
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.
Description quoted from the NVD record.
Who is affected
Flowise is a tool for building apps and chatbots that use AI language models. This flaw affects Flowise versions before 3.0.6, with versions 2.2.8 and earlier named as affected. The parts of the product that save and serve files for chatflows and chats do not check the chat and chatflow identifiers they are given. Because of this, an attacker who does not need to log in can write files anywhere on the server and read any file on it. Writing files may let the attacker run their own commands on the server. This flaw is rated Critical.
What to do
- If someone in your organization installed or runs Flowise, that person should handle this. If an IT provider or vendor runs it for you, send them this advisory and ask when the update will be done.
- Update Flowise to version
3.0.6or later, which fixes this flaw. - Treat this update as urgent, because this flaw can be used without logging in.
- If you are not sure which version your organization runs, ask the person who installed it to check and compare it with version
3.0.6.
Analysis written from the source record as of October 12, 2026 and reviewed before publishing.