CVE-2026-69262

Flowise, an open-source drag & drop UI for building LLM flows, contains an authorization flaw (CWE-863) in the DELETE /api/v1/chatflows/:id endpoint prior to version 3.1.3. The endpoint accepted requests from users holding either the chatflows:delete or agentflows:delete permission, and the delete logic resolved the target record only by id and workspaceId without validating the resource type. As a result, an authenticated user with only agentflows:delete permission could delete a CHATFLOW, and a user with only chatflows:delete could delete an AGENTFLOW within the same workspace — a privilege escalation across resource types. The impact is permanent deletion of other users' flow configurations (high availability impact per CVSS 4.0 score of 7.1), with no direct confidentiality impact. The issue is fixed in version 3.1.3; exploitation likelihood appears low (EPSS 0.3%), with no known in-the-wild abuse and no CISA KEV listing.

What to do: Upgrade Flowise to version 3.1.3 or later, which enforces correct resource-type validation on the delete path. Review role assignments in multi-user deployments and confirm that users who should only manage agentflows (or only chatflows) have not deleted resources of the other type — check API/audit logs for delete operations on mismatched resource types. If upgrade is delayed, restrict access to the Flowise API to trusted, authenticated users only and avoid exposing instances directly to the internet.