CVE-2026-46441: FlowiseAI mass assignment in assistant update endpoint

CVE-2026-46441 · Severity: high · CVSS 4 · Published 2026-06-08

FlowiseAI, a platform for building LLM-based applications, contains a vulnerability that allows users to move AI 'assistants' between different organizational workspaces. An attacker with basic account access could reassign resources to workspaces they do not own, potentially gaining access to sensitive configurations or disrupting other users' operations. This flaw breaks the security boundaries intended to keep different teams or customers isolated from one another.

Technologies: FlowiseAI, flowise (npm). Vendors: FlowiseAI, npm.

Quick answers

Is CVE-2026-46441 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-46441 being exploited in the wild.
How severe is CVE-2026-46441?
High severity, with a CVSS score of 4, published 8 June 2026.
Which products and versions are affected?
FlowiseAI < 3.1.2; flowise (npm) <= 3.1.1, SEMVER:introduced=0,fixed=3.1.2.
Is there a fix for CVE-2026-46441?
Yes. flowise (npm): upgrade to 3.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46441 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-46441?
Check whether you run FlowiseAI or flowise (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • flowise (npm): upgrade to 3.1.2 or later
    npm install flowise@3.1.2

Technical details

A mass assignment vulnerability exists in the FlowiseAI assistant update endpoint (PUT /api/v1/assistants/{assistantId}). The server fails to restrict which properties can be modified by the client, directly mapping user-controlled JSON fields to the underlying database entity without whitelisting. An authenticated attacker can inject server-controlled fields such as 'workspaceId', 'createdDate', and 'updatedDate' into the request body. By manipulating the 'workspaceId', an attacker can reassign assistant resources to arbitrary workspaces, bypassing tenant isolation in multi-workspace environments. The issue is fixed in version 3.1.2.

Affected products

  • FlowiseAI flowise <= 3.1.1

Identifiers

  • CVE-2026-46441
  • GHSA-hp26-q66v-q2w7

Timeline

  • 2026-05-14: disclosed
  • 2026-05-14: advisory
  • 2026-05-14: patched: Fixed in version 3.1.2

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.