CVE-2026-69252

Flowise, an open-source drag & drop UI for building LLM workflows, failed to enforce permission checks on the GET and DELETE methods of its /api/v1/files API route in versions prior to 3.1.3, protecting it only with a feature gate (CWE-862). A low-privileged authenticated API key whose permissions are unrelated to file management could call GET /api/v1/files to enumerate files under the organization's storage root, and DELETE /api/v1/files?path=... to delete files belonging to other workspaces in the same organization, because the getAllFiles and deleteFile handlers used activeOrganizationId plus a user-controlled path without restricting access by permissions or activeWorkspaceId. An attacker gains read access to file listings (high confidentiality impact) and the ability to destroy other workspaces' files (high availability impact), reflected in a CVSS v4.0 score of 7.2. Organizations running self-hosted Flowise before 3.1.3 with multi-workspace setups and distributed API keys are affected. The flaw is fixed in version 3.1.3, a coordinated vendor advisory is public, and no in-the-wild exploitation is known (EPSS 0.3%, not in CISA KEV).

What to do: Upgrade Flowise to version 3.1.3 or later immediately. Review storage volumes and logs for unexpected file deletions or listing activity by low-privileged API keys, and restore any deleted workspace files from backup. As defense in depth, rotate or prune API keys with minimal permissions and avoid exposing self-hosted instances directly to the internet.