Flowise: FlowiseAI has Mass Assignment in Assistant Update Endpoint that Allows Cross-Workspace Resource…
Flowise
More for Flowise RSS feed for Flowise
- Severity
- Critical, CVSS 9.6
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
- Record
- CVE-2026-46441
- Affects
- Flowise
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- June 8, 2026
- Source last modified
- July 23, 2026
Description
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to version 3.1.2, 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. This issue has been patched in version 3.1.2.
Description quoted from the NVD record.
Who is affected
Flowise is a drag-and-drop tool for building apps that use AI language models. This flaw affects all versions before 3.1.2. It is in the part of the product that saves changes to an assistant. Anyone with a login can change details that only the server should set, including which workspace an assistant belongs to, because the product does not check these changes. An attacker with an account could move assistants into other workspaces. This breaks the separation between workspaces in setups that use more than one workspace. This flaw is rated Critical.
What to do
- If you or someone on your staff installed and runs Flowise, that person should check which version is in use.
- Update Flowise to version
3.1.2or later, which fixes this flaw. Any version before 3.1.2 is affected. - If an IT provider or vendor runs Flowise for your organization, send them this advisory and ask when the update will be done.
- After updating, check that each assistant is still in the workspace where it belongs, especially if your setup uses more than one workspace.
Analysis written from the source record as of July 23, 2026 and reviewed before publishing.