CVE-2026-69262 in Flowise
Summary
by MITRE • 08/04/2026
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, `DELETE /api/v1/chatflows/:id` authorized requests with checkAnyPermission('chatflows:delete,agentflows:delete'), so possession of either permission was sufficient to reach the delete path. The delete logic then resolved the target record only by id and workspaceId and did not validate the target resource type, allowing a caller with only agentflows:delete to delete a CHATFLOW and a caller with only chatflows:delete to delete an AGENTFLOW in the same workspace. This issue is fixed in version 3.1.3.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 08/04/2026
The vulnerability identified in Flowise versions prior to 3.1.3 represents a critical authorization bypass flaw that undermines the application's access control mechanisms. This issue manifests in the DELETE /api/v1/chatflows/:id endpoint where the system employs a permissive permission checking strategy using checkAnyPermission('chatflows:delete,agentflows:delete'). The flawed implementation allows unauthorized deletion of resources by leveraging the principle of least privilege incorrectly, creating a scenario where individual permissions can be exploited to access functionality beyond their intended scope. The vulnerability stems from insufficient validation logic that fails to properly verify resource types during deletion operations, enabling cross-type resource manipulation.
The technical implementation flaw occurs when the delete logic resolves target records based solely on id and workspaceId parameters without performing adequate type validation. This design oversight creates a path where a malicious actor possessing only one of the two available permissions can exploit the system's weak authorization boundaries to delete resources of the opposite type. Specifically, a user with agentflows:delete permission can delete CHATFLOW resources while a user with chatflows:delete permission can delete AGENTFLOW resources within the same workspace, effectively bypassing the intended separation of concerns between different resource types.
This authorization bypass has significant operational impact on system security and data integrity. The vulnerability allows for unauthorized modification of critical application components that could result in loss of configuration data, disruption of service availability, and potential compromise of sensitive information stored within deleted resources. The cross-type deletion capability creates an attack surface where attackers can systematically target different resource categories within the same workspace, amplifying the potential damage from a single compromised permission. Organizations relying on Flowise for large language model workflow management face increased risk of unauthorized modifications to their chatflow and agentflow configurations.
The vulnerability aligns with CWE-285 (Improper Authorization) and represents an instance of privilege escalation through improper access control validation. From an ATT&CK framework perspective, this issue maps to T1078 (Valid Accounts) and T1531 (Account Access Removal) where unauthorized deletion operations can lead to account access disruption and data loss. The fix implemented in version 3.1.3 addresses the root cause by strengthening authorization checks to validate resource types before permitting deletion operations, ensuring that users cannot delete resources of a different type than what their permissions explicitly authorize.
Organizations should immediately upgrade to Flowise version 3.1.3 or later to remediate this vulnerability and implement additional monitoring for unauthorized deletion activities. System administrators should review existing permission assignments to minimize the risk of privilege escalation and ensure proper separation of duties between different resource types. The mitigation strategy should include enhanced audit logging of deletion operations and regular security assessments to identify potential authorization boundary violations in similar applications. This vulnerability demonstrates the critical importance of type validation in API endpoints and highlights the need for comprehensive authorization testing during security reviews.