CVE-2026-70471: CWE-863: Incorrect Authorization in FlowiseAI Flowise
Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. Prior to 3.1.3, Flowise injects $vars into the code execution sandbox without requiring variables:view, bypassing the permission-protected Variables API. Variables for the active workspace are fetched at packages/components/src/utils.ts and runtime variables are resolved from server environment variables, while the official variables route enforces variables:view. A user or API key that is denied variables:view can call /api/v1/node-custom-function and receive $vars pre-populated with all variables for the workspace, including Variable.name to Variable.value static variables and Variable.name to process.env[Variable.name] runtime variables. This can expose secrets such as database passwords, JWT secrets, SMTP passwords, and cloud keys, depending on the workspace Variables configuration. This issue is fixed in version 3.1.3.
AI Analysis
Technical Summary
CVE-2026-70471 is an incorrect authorization vulnerability (CWE-863) in FlowiseAI's Flowise product before version 3.1.3. The vulnerability arises because the application injects $vars into the code execution sandbox without enforcing the variables:view permission required by the official Variables API. Consequently, unauthorized users or API keys can call the /api/v1/node-custom-function endpoint and receive $vars pre-populated with all workspace variables, including static and runtime environment variables. This exposure can leak sensitive secrets configured in the workspace variables. The vulnerability is resolved in Flowise version 3.1.3.
Potential Impact
Unauthorized users or API keys lacking variables:view permission can access sensitive workspace variables, potentially exposing secrets such as database passwords, JWT secrets, SMTP passwords, and cloud keys. This can lead to compromise of confidential information and downstream systems relying on these secrets.
Mitigation Recommendations
Upgrade Flowise to version 3.1.3 or later, where this authorization bypass vulnerability is fixed. No other mitigations are specified. Patch status is confirmed by the vendor advisory stating the issue is fixed in 3.1.3.
CVE-2026-70471: CWE-863: Incorrect Authorization in FlowiseAI Flowise
Description
Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. Prior to 3.1.3, Flowise injects $vars into the code execution sandbox without requiring variables:view, bypassing the permission-protected Variables API. Variables for the active workspace are fetched at packages/components/src/utils.ts and runtime variables are resolved from server environment variables, while the official variables route enforces variables:view. A user or API key that is denied variables:view can call /api/v1/node-custom-function and receive $vars pre-populated with all variables for the workspace, including Variable.name to Variable.value static variables and Variable.name to process.env[Variable.name] runtime variables. This can expose secrets such as database passwords, JWT secrets, SMTP passwords, and cloud keys, depending on the workspace Variables configuration. This issue is fixed in version 3.1.3.
CVSS v4.0
Score 7.1high
Affected software
FlowiseAI
Flowise
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-70471 is an incorrect authorization vulnerability (CWE-863) in FlowiseAI's Flowise product before version 3.1.3. The vulnerability arises because the application injects $vars into the code execution sandbox without enforcing the variables:view permission required by the official Variables API. Consequently, unauthorized users or API keys can call the /api/v1/node-custom-function endpoint and receive $vars pre-populated with all workspace variables, including static and runtime environment variables. This exposure can leak sensitive secrets configured in the workspace variables. The vulnerability is resolved in Flowise version 3.1.3.
Potential Impact
Unauthorized users or API keys lacking variables:view permission can access sensitive workspace variables, potentially exposing secrets such as database passwords, JWT secrets, SMTP passwords, and cloud keys. This can lead to compromise of confidential information and downstream systems relying on these secrets.
Mitigation Recommendations
Upgrade Flowise to version 3.1.3 or later, where this authorization bypass vulnerability is fixed. No other mitigations are specified. Patch status is confirmed by the vendor advisory stating the issue is fixed in 3.1.3.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-04T15:24:41.339Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a723098bf8831d5393f8dd9
Added to database: 08/04/2026, 18:34:00 UTC
Last enriched: 08/04/2026, 18:41:56 UTC
Last updated: 09/18/2026, 22:01:37 UTC
Views: 66
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.
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.