CVE-2026-71962 in Flowise
Summary
by MITRE • 08/10/2026
Flowise versions 2.2.4 through 3.1.4 contain a missing authorization vulnerability in the POST /api/v1/openai-assistants-file/download endpoint that allows unauthenticated attackers to access private files by exploiting the endpoint's inclusion in the global authentication whitelist, which bypasses all session and API key verification. Attackers can supply valid chatflowId, chatId, and fileName identifiers to retrieve files from any chatflow on the instance, including private chatflows belonging to other workspaces or organizations.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 08/10/2026
This vulnerability exists within Flowise versions 2.2.4 through 3.1.4 where the POST /api/v1/openai-assistants-file/download endpoint suffers from a critical missing authorization flaw that fundamentally undermines the application's security model. The technical implementation error stems from improper access control enforcement at the API layer, specifically allowing unauthenticated requests to bypass all authentication mechanisms. The vulnerability manifests because this particular endpoint has been inadvertently included in a global authentication whitelist, creating an unauthorized access vector that operates outside normal session and API key verification procedures. This misconfiguration enables attackers to exploit the endpoint without providing any valid credentials, effectively neutralizing all security controls that should normally protect private file access within the application's multi-tenant architecture.
The operational impact of this vulnerability is severe and far-reaching, as it allows adversaries to retrieve files from any chatflow on the Flowise instance regardless of ownership or authorization status. Attackers can leverage valid identifiers including chatflowId, chatId, and fileName parameters to access private data that should only be available to authorized users within specific workspaces or organizations. This creates a significant risk for organizations using Flowise in production environments where sensitive information may be stored within chatflows, potentially exposing confidential documents, proprietary data, or personal information belonging to other users or organizations. The vulnerability essentially transforms the application's file access controls into a public interface, enabling data exfiltration across organizational boundaries and potentially leading to compliance violations under data protection regulations.
The security implications extend beyond simple unauthorized file access, as this vulnerability aligns with CWE-863 (Authorization Bypass Through User-Controlled Key) and represents a classic case of insecure direct object reference where attackers can manipulate identifiers to access resources they shouldn't have permission to view. From an attack framework perspective, this vulnerability maps to multiple ATT&CK techniques including T1078 (Valid Accounts) and T1566 (Phishing), as it allows attackers to exploit legitimate identifiers within the system without requiring additional credential compromise. The vulnerability also demonstrates poor principle of least privilege implementation, where the endpoint's access control logic fails to properly validate user permissions against the requested resources.
Organizations should immediately implement mitigations including restricting access to the vulnerable endpoint through network-level controls, implementing proper authentication enforcement for all file download operations, and conducting comprehensive access control reviews across all API endpoints. The recommended remediation involves removing the endpoint from any global authentication whitelist, enforcing strict authorization checks that validate user permissions against requested resources, and implementing rate limiting to prevent automated exploitation attempts. Additionally, organizations should consider implementing API gateway controls to monitor and restrict access patterns to sensitive endpoints, while also performing regular security assessments to identify similar misconfigurations within their application architecture that could potentially expose other data assets within the system.