CVE-2026-41277: CWE-284: Improper Access Control in FlowiseAI Flowise
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, a Mass Assignment vulnerability in the DocumentStore creation endpoint allows authenticated users to control the primary key (id) and internal state fields of DocumentStore entities. Because the service uses repository.save() with a client-supplied primary key, the POST create endpoint behaves as an implicit UPSERT operation. This enables overwriting existing DocumentStore objects. In multi-workspace or multi-tenant deployments, this can lead to cross-workspace object takeover and broken object-level authorization (IDOR), allowing an attacker to reassign or modify DocumentStore objects belonging to other workspaces. This vulnerability is fixed in 3.1.0.
AI Analysis
Technical Summary
CVE-2026-41277 is an improper access control vulnerability (CWE-284) in FlowiseAI Flowise before version 3.1.0. The flaw arises from a Mass Assignment issue in the DocumentStore creation endpoint, where authenticated users can supply a primary key (id) and internal state fields. The service uses repository.save() with the client-supplied primary key, causing the POST create endpoint to behave as an implicit UPSERT, allowing overwriting of existing DocumentStore objects. In multi-workspace or multi-tenant deployments, this leads to broken object-level authorization (IDOR), enabling attackers to take over or modify DocumentStore objects from other workspaces. The vulnerability is resolved in version 3.1.0.
Potential Impact
The vulnerability allows authenticated users to overwrite existing DocumentStore objects by controlling the primary key and internal state fields. In multi-tenant or multi-workspace setups, this results in cross-workspace object takeover and broken object-level authorization, potentially compromising data integrity and confidentiality across different workspaces. There are no known exploits in the wild as of the published date.
Mitigation Recommendations
This vulnerability is fixed in Flowise version 3.1.0. Users should upgrade to version 3.1.0 or later to remediate the issue. Patch status is not explicitly stated beyond this fix version, so verify with the vendor advisory for the latest remediation guidance.
CVE-2026-41277: CWE-284: Improper Access Control in FlowiseAI Flowise
Description
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, a Mass Assignment vulnerability in the DocumentStore creation endpoint allows authenticated users to control the primary key (id) and internal state fields of DocumentStore entities. Because the service uses repository.save() with a client-supplied primary key, the POST create endpoint behaves as an implicit UPSERT operation. This enables overwriting existing DocumentStore objects. In multi-workspace or multi-tenant deployments, this can lead to cross-workspace object takeover and broken object-level authorization (IDOR), allowing an attacker to reassign or modify DocumentStore objects belonging to other workspaces. This vulnerability is fixed in 3.1.0.
CVSS v4.0
Score 7.6high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-41277 is an improper access control vulnerability (CWE-284) in FlowiseAI Flowise before version 3.1.0. The flaw arises from a Mass Assignment issue in the DocumentStore creation endpoint, where authenticated users can supply a primary key (id) and internal state fields. The service uses repository.save() with the client-supplied primary key, causing the POST create endpoint to behave as an implicit UPSERT, allowing overwriting of existing DocumentStore objects. In multi-workspace or multi-tenant deployments, this leads to broken object-level authorization (IDOR), enabling attackers to take over or modify DocumentStore objects from other workspaces. The vulnerability is resolved in version 3.1.0.
Potential Impact
The vulnerability allows authenticated users to overwrite existing DocumentStore objects by controlling the primary key and internal state fields. In multi-tenant or multi-workspace setups, this results in cross-workspace object takeover and broken object-level authorization, potentially compromising data integrity and confidentiality across different workspaces. There are no known exploits in the wild as of the published date.
Mitigation Recommendations
This vulnerability is fixed in Flowise version 3.1.0. Users should upgrade to version 3.1.0 or later to remediate the issue. Patch status is not explicitly stated beyond this fix version, so verify with the vendor advisory for the latest remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-18T14:01:46.802Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69ea9e7887115cfb686fc38c
Added to database: 4/23/2026, 10:34:32 PM
Last enriched: 5/1/2026, 8:40:47 PM
Last updated: 6/7/2026, 8:05:02 AM
Views: 92
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.