Flowise CVE-2026-69262

Exploitation requires an authenticated caller with a valid Flowise API key or session bearing at least one of chatflows:delete or agentflows:delete permissions within a workspace running Flowise 3.1.2 or earlier. The target flow must exist in the same workspaceId as the caller - cross-workspace deletion is not possible. No special network position, non-default configuration, or privilege escalation is required beyond standard workspace membership with one of these two delete permissions. Exploitation is strictly scoped to irreversible deletion of flows within the attacker's workspace; there is no confidentiality exposure, no code execution, and no impact on other workspaces. Organization admins are not affected by this flaw because they already possess full permissions by design.

The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N, score 7.1) accurately characterizes the threat: network-reachable, low complexity, requiring only low-privilege authentication, with impact confined to availability - irreversible deletion of flows. There is no confidentiality or integrity impact to data contents. No EPSS data was provided in the source intelligence; given Flowise's niche deployment footprint and the requirement for valid workspace credentials, broad opportunistic scanning is unlikely. There is no CISA KEV listing confirming active exploitation. The GHSA advisory supplies a detailed curl reproduction command, which constitutes low-friction exploit guidance for any authenticated workspace member - the practical bar for abuse is therefore very low once an attacker holds any delete permission. Risk is highest in multi-tenant Flowise workspaces where separation of chatflow and agentflow administrative rights is a meaningful security boundary. Organizations running single-user or fully-trusted-workspace deployments face negligible incremental risk.

An authenticated workspace member who has been granted only the agentflows:delete API key permission - for example, an automation account managing agent pipelines - enumerates chatflow IDs via the workspace API and sends a DELETE request to /api/v1/chatflows/<chatflow_id> using their restricted API key. The server accepts the request because the route's permission check passes (the caller holds one of the two allowed permissions), and the service deletes the CHATFLOW without validating the resource type. The GHSA advisory includes a verbatim curl command that reproduces the 200 OK response and confirmed deletion, requiring no additional tooling beyond a valid API key.