CVE-2026-42861: FlowiseAI Flowise · Improper Access Control
Affects FlowiseAI FlowiseSource CVE Database V5
Not known to be exploited · CVSS 7.6 High : upgrade to 3.1.2 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.1.2
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Flowise and flowiseai/Flowise to 3.1.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| FlowiseAIFlowise | Affected
| Fixed in
|
GitHubflowiseai/Flowisepkg:github/flowiseai/FlowiseOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in FlowiseAI Flowise version 3.1.2. Users should upgrade to version 3.1.2 or later to remediate this vulnerability. Since the vendor advisory does not provide additional mitigation steps, upgrading is the primary recommended action.
Description
FlowiseAI Flowise versions prior to 3.1.2 contain a mass assignment vulnerability in the variable update endpoint. Authenticated users can modify server-controlled properties such as workspaceId without proper authorization checks, allowing reassignment of variables to arbitrary workspaces. This can break tenant isolation in multi-workspace environments. The issue has been fixed in version 3.1.2.