CVE-2026-41267: CWE-639: Authorization Bypass Through User-Controlled Key in FlowiseAI Flowise
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, an improper mass assignment (JSON injection) vulnerability in the account registration endpoint of Flowise Cloud allows unauthenticated attackers to inject server-managed fields and nested objects during account creation. This enables client-controlled manipulation of ownership metadata, timestamps, organization association, and role mappings, breaking trust boundaries in a multi-tenant environment. This vulnerability is fixed in 3.1.0.
AI Analysis
Technical Summary
CVE-2026-41267 is an authorization bypass vulnerability in FlowiseAI's Flowise product before version 3.1.0. It arises from improper mass assignment in the account registration endpoint, enabling unauthenticated attackers to inject and control server-managed fields and nested objects during account creation. This allows manipulation of critical metadata and role mappings, violating trust boundaries in multi-tenant deployments. The vulnerability is tracked under CWE-639 (Authorization Bypass Through User-Controlled Key) and CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes). The CVSS v3.1 base score is 8.1, indicating high severity. The issue is resolved in Flowise version 3.1.0.
Potential Impact
Successful exploitation allows unauthenticated attackers to bypass authorization controls by injecting server-managed fields during account registration. This can lead to unauthorized modification of ownership metadata, timestamps, organization associations, and role mappings, potentially compromising multi-tenant isolation and enabling privilege escalation or data access violations. The impact includes full confidentiality, integrity, and availability compromise as indicated by the CVSS vector.
Mitigation Recommendations
Upgrade Flowise to version 3.1.0 or later, where this vulnerability is fixed. Since the vendor advisory confirms the fix in 3.1.0, applying this official update is the recommended remediation. Patch status is not explicitly stated beyond this version fix, so verify with the vendor for any additional guidance or patches.
CVE-2026-41267: CWE-639: Authorization Bypass Through User-Controlled Key in FlowiseAI Flowise
Description
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, an improper mass assignment (JSON injection) vulnerability in the account registration endpoint of Flowise Cloud allows unauthenticated attackers to inject server-managed fields and nested objects during account creation. This enables client-controlled manipulation of ownership metadata, timestamps, organization association, and role mappings, breaking trust boundaries in a multi-tenant environment. This vulnerability is fixed in 3.1.0.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-41267 is an authorization bypass vulnerability in FlowiseAI's Flowise product before version 3.1.0. It arises from improper mass assignment in the account registration endpoint, enabling unauthenticated attackers to inject and control server-managed fields and nested objects during account creation. This allows manipulation of critical metadata and role mappings, violating trust boundaries in multi-tenant deployments. The vulnerability is tracked under CWE-639 (Authorization Bypass Through User-Controlled Key) and CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes). The CVSS v3.1 base score is 8.1, indicating high severity. The issue is resolved in Flowise version 3.1.0.
Potential Impact
Successful exploitation allows unauthenticated attackers to bypass authorization controls by injecting server-managed fields during account registration. This can lead to unauthorized modification of ownership metadata, timestamps, organization associations, and role mappings, potentially compromising multi-tenant isolation and enabling privilege escalation or data access violations. The impact includes full confidentiality, integrity, and availability compromise as indicated by the CVSS vector.
Mitigation Recommendations
Upgrade Flowise to version 3.1.0 or later, where this vulnerability is fixed. Since the vendor advisory confirms the fix in 3.1.0, applying this official update is the recommended remediation. Patch status is not explicitly stated beyond this version fix, so verify with the vendor for any additional guidance or patches.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-18T14:01:46.801Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69ea782987115cfb6850f827
Added to database: 4/23/2026, 7:51:05 PM
Last enriched: 4/23/2026, 8:06:48 PM
Last updated: 4/24/2026, 6:06:02 AM
Views: 8
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.