FlowiseAI Chatflow Update Endpoint Mass Assignment Vulnerability
A mass assignment vulnerability exists in FlowiseAI's chatflow update endpoint (CVE-2026-42863), allowing authenticated users to modify server-controlled properties like `deployed`, `isPublic`, and `workspaceId` due to missing server-side validation, leading to cross-workspace resource reassignment and unauthorized modification of deployment and visibility settings.
A mass assignment vulnerability has been identified in FlowiseAI versions 3.1.1 and earlier. The vulnerability resides in the chatflow update endpoint, which lacks proper server-side validation and authorization checks. This allows authenticated users to manipulate server-controlled properties of chatflow objects, such as deployed, isPublic, and workspaceId, by including them in the request body. By exploiting this flaw, an attacker can reassign chatflows to different workspaces, modify deployment settings, and alter visibility settings, potentially leading to unauthorized access and control over resources in multi-tenant environments. This vulnerability is identified as CVE-2026-42863.
Attack Chain
- The attacker authenticates to the FlowiseAI interface with valid credentials.
- The attacker captures a legitimate request used to update a chatflow object via the
PUT /api/v1/chatflows/{chatflowId}endpoint. - The attacker modifies the captured request body to include server-controlled fields such as
deployed,isPublic, andworkspaceId. - The attacker sets the
workspaceIdto the ID of a workspace controlled by the attacker. - The attacker sends the crafted request to the
/api/v1/chatflows/{chatflowId}endpoint. - The FlowiseAI server accepts the modified request and updates the chatflow object in the database without proper validation.
- The chatflow is now reassigned to the attacker’s workspace, granting the attacker unauthorized access.
- The attacker can further modify the chatflow, change its visibility, or alter its deployment status.
Impact
The mass assignment vulnerability in FlowiseAI allows authenticated users to manipulate server-controlled attributes of chatflows. This can result in unauthorized modification of chatflow visibility, deployment state changes, and cross-workspace reassignment of chatflows. In multi-tenant environments, this vulnerability breaks tenant isolation boundaries, enabling attackers to move chatflows between workspaces without authorization. Successful exploitation can lead to cross-workspace workflow takeover, unauthorized exposure of private workflows, and manipulation of deployed agent workflows, potentially affecting all FlowiseAI installations with versions 3.1.1 or lower.
Recommendation
- Deploy the Sigma rule “Detect FlowiseAI Chatflow Mass Assignment Attempt via API” to detect attempts to modify restricted fields via the chatflow update API endpoint.
- Apply input validation to the
PUT /api/v1/chatflows/{chatflowId}endpoint to prevent modification ofdeployed,isPublic,workspaceId,createdDate,updatedDate,category, andtypeparameters, mitigating CVE-2026-42863. - Upgrade FlowiseAI to a patched version that addresses the mass assignment vulnerability to prevent unauthorized modification of chatflow attributes, protecting against CVE-2026-42863.
Detection coverage 2
Detect FlowiseAI Chatflow Mass Assignment Attempt via API
highDetects CVE-2026-42863 exploitation — Attempts to modify restricted fields in FlowiseAI's chatflow update API endpoint, indicating a mass assignment vulnerability exploitation attempt.
Detect FlowiseAI Chatflow Mass Assignment Successful Modification
mediumDetects CVE-2026-42863 exploitation — Monitors successful modification of server-controlled fields. Requires correlation with other logs.
Detection queries are available on the platform. Get full rules →