Flowise: FlowiseAI has Mass Assignment in Chatflow Update Endpoint that Allows Cross-Workspace AgentFlow…
Flowise
More for Flowise RSS feed for Flowise
- Severity
- High, CVSS 8.1
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- Record
- CVE-2026-42863
- 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 chatflow update endpoint of FlowiseAI. The endpoint allows clients to modify server-controlled properties such as deployed, isPublic, workspaceId, createdDate, and updatedDate when updating a chatflow object. Due to missing server-side validation and authorization checks, an authenticated user can manipulate internal attributes of a chatflow and reassign it to another workspace. This allows cross-workspace resource reassignment and unauthorized modification of deployment and visibility settings. 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 chatbots and other apps that use AI language models. This flaw affects all versions before 3.1.2. It sits in the part of the product that saves changes to a chatflow (a chatbot or AI workflow built in Flowise). Because Flowise does not properly check these changes, anyone with a login to your Flowise system could alter settings they should not control. They could move a chatflow into another workspace, and change whether it is deployed or publicly visible. This flaw is rated High.
What to do
- If you or someone in your organization installed and runs Flowise, that person should check which version is in use.
- If the version is older than
3.1.2, update Flowise to version3.1.2or later, which fixes this flaw. - If an IT provider or vendor runs Flowise for your organization, send them this advisory and ask when the update to
3.1.2will be done. - After updating, review your chatflows to check that each one is in the right workspace and that its deployment and public visibility settings are as you expect.
Analysis written from the source record as of July 23, 2026 and reviewed before publishing.