FlowiseAI Mass Assignment Vulnerability in Variable Update Endpoint
FlowiseAI versions 3.1.1 and earlier contain a mass assignment vulnerability in the variable update endpoint allowing authenticated users to modify server-controlled properties like workspaceId, createdDate, and updatedDate, potentially breaking tenant isolation in multi-workspace environments (CVE-2026-42861).
FlowiseAI, a low-code platform for building AI workflows, is vulnerable to a mass assignment flaw (CVE-2026-42861) affecting versions 3.1.1 and earlier. The vulnerability resides in the /api/v1/variables/{variableId} endpoint, which is used for updating variable resources. Due to missing server-side validation, an authenticated attacker can modify critical, server-controlled properties such as workspaceId, createdDate, and updatedDate. This can lead to unauthorized cross-workspace reassignment of variables, potentially compromising tenant isolation in multi-tenant environments. The issue was reported in May 2026, and defenders need to implement mitigations to prevent unauthorized data access and manipulation.
Attack Chain
- Attacker authenticates to FlowiseAI with valid user credentials.
- Attacker identifies a target variable ID within the application they wish to manipulate.
- Attacker crafts a malicious PUT request to
/api/v1/variables/{variableId}. - The request body includes the
workspaceIdfield, setting it to the ID of a different workspace the attacker wishes to access. - The request body may also include modified
createdDateandupdatedDatevalues for the variable. - The FlowiseAI server, lacking proper validation, accepts the attacker-supplied
workspaceId,createdDate, andupdatedDatevalues. - The server updates the variable in the database with the attacker-controlled values, effectively reassigning the variable to the attacker’s chosen workspace.
- The attacker can now access and potentially manipulate resources within the targeted workspace using the reassigned variable.
Impact
Successful exploitation allows authenticated users to manipulate internal variable attributes, potentially leading to cross-workspace reassignment of variables, unauthorized modification of metadata, and tenant isolation bypass in multi-workspace deployments. This can allow an attacker to move variables between workspaces without proper authorization. The vulnerability affects FlowiseAI installations version 3.1.1 and earlier.
Recommendation
- Apply input validation and authorization checks on the
/api/v1/variables/{variableId}endpoint to prevent modification of server-controlled properties likeworkspaceId,createdDate, andupdatedDateas described in CVE-2026-42861. - Monitor PUT requests to the
/api/v1/variables/{variableId}endpoint for attempts to modify theworkspaceIdparameter to detect potential exploitation attempts. Use the detection ruleDetect FlowiseAI Mass Assignment in Variable Updateto identify anomalous requests. - Implement workspace access controls and verify that users can only access variables within their assigned workspace, regardless of the
workspaceIdattribute.
Detection coverage 2
Detect FlowiseAI Mass Assignment in Variable Update
highDetects attempts to exploit the FlowiseAI mass assignment vulnerability (CVE-2026-42861) by monitoring PUT requests to the variable update endpoint with modifications to restricted fields.
Detect FlowiseAI suspicious date manipulation
mediumDetects attempts to exploit CVE-2026-42861 by looking for unusual dates in the updatedDate and createdDate fields. Requires webserver logs.
Detection queries are available on the platform. Get full rules →