Flowise: Flowise through 2.2.7 fails to sanitize path segments in the document-store loader endpoint…
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-71338
- 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 through 2.2.7 fails to sanitize path segments in the document-store loader endpoint, allowing unauthenticated attackers to write files outside the storage directory. Attackers can use parent-directory sequences to escape the storage directory and overwrite application files loaded at boot for remote code execution.
Description quoted from the NVD record.
Who is affected
Flowise is a tool for building apps that use AI language models. This flaw affects Flowise versions through 2.2.7. It is in the part of the product that loads documents into its document storage. Because that part does not properly check file locations it is given, an attacker who has not logged in can save files outside the storage area. By replacing program files that Flowise loads when it starts up, the attacker could then run their own commands on the computer running Flowise. This flaw is rated Critical.
What to do
- If your organization installed and runs Flowise itself, the person who set it up should check which version is in use. Versions through 2.2.7 are affected.
- No fixed version is named for this flaw yet, so check the vendor advisory linked on this page for a fixed release, and install it as soon as one is available.
- If an IT provider or vendor runs Flowise for your organization, send them this advisory and ask when the update will be done.
Analysis written from the source record as of October 12, 2026 and reviewed before publishing.