Quick answers
- Is CVE-2026-46476 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46476 being exploited in the wild.
- How severe is CVE-2026-46476?
- High severity, with a CVSS score of 4, published 8 June 2026.
- Which products and versions are affected?
- FlowiseAI <= 3.1.1; flowise (npm) <= 3.1.1, SEMVER:introduced=0,fixed=3.1.2.
- Is there a fix for CVE-2026-46476?
- 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-46476 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-46476?
- 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 CustomTemplate service due to the use of Object.assign() on the request body without an explicit field allowlist. An authenticated attacker can include a 'workspaceId' in a create or update request to reassign a template to a different workspace. This breaks workspace isolation and allows for cross-workspace data takeover or Insecure Direct Object Reference (IDOR) attacks. The vulnerability is located in 'packages/server/src/services/marketplaces/index.ts'. A fix is available in version 3.1.2 which implements a strict allowlist for object properties.
Affected products
- FlowiseAI FlowiseAI <= 3.1.1
Identifiers
- CVE-2026-46476
- GHSA-728h-4mwj-f2p4
Timeline
- 2026-05-14: disclosed
- 2026-05-14: patched: Fixed in version 3.1.2
- 2026-05-14: advisory