Flowise: Flowise before 3.0.6 contains an arbitrary file read vulnerability in the chatId parameter of…
Flowise
More for Flowise RSS feed for Flowise
- Severity
- High, CVSS 7.5
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Record
- CVE-2025-71324
- 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 contains an arbitrary file read vulnerability in the chatId parameter of the /api/v1/get-upload-file and /api/v1/openai-assistants-file/download endpoints. The chatId value is not validated and is passed to streamStorageFile(), where a fallback file-lookup path constructed without the orgId is evaluated after the storage-directory containment check, allowing path traversal beyond the intended storage directory. Unauthenticated attackers can read sensitive files such as /root/.flowise/database.sqlite, exposing all database content in the default configuration.
Description quoted from the NVD record.
Who is affected
Flowise, a tool for building apps that use AI language models, has a flaw in the parts that let people download uploaded files and files used by OpenAI assistants. This flaw affects versions before 3.0.6. Because a chat identifier sent to these parts is not checked properly, an attacker can reach outside the folder where Flowise keeps stored files. The attacker does not need to log in and can read sensitive files on the server, such as the Flowise database, which in the default setup exposes all of its contents. This flaw is rated High.
What to do
- Find out who runs Flowise for your organization: the person who installed it, or the IT provider or vendor that manages it.
- If your organization runs it itself, that person should update Flowise to version
3.0.6or later, which fixes this flaw. - If an IT provider or vendor runs Flowise for you, send them this advisory and ask when the update will be done.
- No workaround or setting change is named for this flaw, so updating is the way to fix it. Check the vendor advisory linked on this page for full details.
Analysis written from the source record as of October 12, 2026 and reviewed before publishing.