Browse / AI Framework and Platform Flaws / CVE-2026-46441
FlowiseAI has Mass Assignment in Assistant Update Endpoint that Allows Cross-Workspace Resource Reassignment
- Class
- AI Framework and Platform Flaws (filed by a model that read the advisory)
- Technique
- Authentication and access control
- Affected
- flowise (npm)
- CVSS
- CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- EPSS
- 0.3% chance of exploitation in 30 days
How it works, in short
The assistant update endpoint copies client-supplied server-owned fields such as workspaceId into the database, letting users move assistants across workspaces. (Our summary, written by a model. The source text is below.)
Details
Summary
A Mass Assignment vulnerability exists in the assistant update endpoint of FlowiseAI.
The endpoint allows authenticated users to modify server-controlled properties such as workspaceId, createdDate, and updatedDate when updating an assistant resource.
Due to missing server-side validation and authorization checks, an attacker can manipulate the workspaceId field and reassign assistants to arbitrary workspaces. This breaks tenant isolation in multi-workspace environments.
Details
The endpoint responsible for updating assistants:
PUT /api/v1/assistants/{assistantId}
accepts a JSON request body containing assistant metadata.
However, the server does not restrict which properties may be modified by the client. As a result, user-controlled request bodies can include additional fields that should normally be controlled only by the backend.
Server-controlled fields that can be manipulated include:
- workspaceId
- createdDate
- updatedDate
These fields appear to be directly mapped to the underlying database entity without strict DTO whitelisting or authorization checks.
For example, the following request body was accepted:
{
"details": "",
"credential": "11ca7fef-c9b1-4c87-aa54-e547aed8a249",
"iconSrc": null,
"type": "CUSTOM",
"createdDate": "2026-03-06T17:31:04.000Z",
"updatedDate": "2026-03-06T17:31:55.000Z",
"workspaceId": "11111111-2222-3333-4444-555555555555"
}
This indicates that internal, server-controlled properties can be modified by an authenticated user.
PoC
- Authenticate to the Flowise interface.
- Capture the request used to update an assistant:
PUT /api/v1/assistants/<ASSISTANT_ID>
Content-Type: application/json
Modify the request body by injecting server-controlled fields:
{
"details": "",
"credential": "11ca7fef-c9b1-4c87-aa54-e547aed8a249",
"iconSrc": null,
"type": "CUSTOM",
"createdDate": "2026-03-06T17:31:04.000Z",
"updatedDate": "2026-03-06T17:31:55.000Z",
"workspaceId": "11111111-2222-3333-4444-555555555555"
}
3.Send the request.
Observe that the response accepts and persists the attacker-controlled workspaceId and metadata fields.
Impact
This vulnerability allows authenticated users to manipulate internal attributes of assistant resources.
Confirmed impacts include:
- Cross-workspace reassignment of assistants (workspaceId)
- Unauthorized modification of metadata (createdDate, updatedDate)
In multi-tenant deployments, this may allow an attacker to move assistants between workspaces without authorization, breaking tenant isolation boundaries.
References
- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-hp26-q66v-q2w7
- https://nvd.nist.gov/vuln/detail/CVE-2026-46441
- https://github.com/FlowiseAI/Flowise
- https://github.com/FlowiseAI/Flowise/releases/tag/flowise%403.1.2
Source: GitHub Advisory Database, used under CC BY 4.0.