CVE-2026-71962

Flowise 2.2.4 - 3.1.4 Missing Authorization via openai-assistants-file/download

Published Aug 10, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The missing authorization in the POST /api/v1/openai-assistants-file/download endpoint allows an unauthenticated attacker to retrieve any private file from any chatflow. By supplying a valid chatflowId, chatId, and fileName, a malicious actor can download content belonging to other workspaces or organizations. The flaw bypasses all session and API key checks because the endpoint is mistakenly included in the global authentication whitelist, undermining data confidentiality.

Affected Systems

The vulnerability affects FlowiseAI Flowise installations running versions 2.2.4 through 3.1.4 inclusive. All tenants on the instance are at risk if they host private chatflows or files.

Risk and Exploitability

The CVSS score of 8.7 indicates high severity. No EPSS score is available, and the vulnerability is not listed in the CISA KEV catalog, but the lack of authentication makes exploitation trivial for any actor with network access to the API. Attackers can trigger the download via an unauthenticated HTTP POST request without needing credentials, making the attack surface wide and easy to leverage.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Flowise to a version later than 3.1.4 that removes the openai-assistants-file/download endpoint from the authentication whitelist.
  • If an immediate upgrade is not feasible, restrict external access to the /api/v1/openai-assistants-file/download endpoint using firewall rules or network policies so only trusted IPs can reach it.
  • Modify the Flowise configuration to remove the endpoint from any global authentication whitelist, ensuring session and API key verification are enforced for all API calls.

Generated by OpenCVE AI on August 10, 2026 at 19:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Flowiseai
Flowiseai flowise
Vendors & Products Flowiseai
Flowiseai flowise
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Flowise 2.2.4 - 3.1.4 Missing Authorization via openai-assistants-file/download
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Aug 14, 2026, 4:51 PM
Reserved
Aug 8, 2026, 4:43 PM
Status
Analyzed
Published
Aug 10, 2026, 7:17 PM
Modified
Oct 24, 2026, 3:10 PM