CVE-2026-71962 is a high severity (CVSS 7.5) missing authorization flaw in Flowise 2.2.4 through 3.1.4. The openai-assistants-file/download endpoint is on the authentication whitelist, so an unauthenticated user can fetch files from any chatflow. I could not confirm a fixed version, and the project is being sunset.
What's affected
Flowise versions 2.2.4 through 3.1.4, according to the record and VulnCheck. Neither names a fixed version. Fixes for the other 2026 Flowise advisories landed in 3.1.3, but this issue reaches 3.1.4, so 3.1.3 is not a fix for this CVE.
The weakness is CWE-862. The POST /api/v1/openai-assistants-file/download endpoint is included in the global authentication whitelist, which skips session and API key checks. A caller who supplies valid chatflowId, chatId and fileName values can retrieve files from any chatflow on the instance, including private ones in other workspaces.
Severity differs by source. The record scores 7.5 high. VulnCheck lists 8.7, high, using a CVSS 4.0 vector. Both agree on no privileges and high confidentiality impact.
The Flowise sunset page says the repository was to be archived on 10 August 2026 and packages marked deprecated, so a patched release may not arrive.
How to check if you're exposed
Check your version:
npm ls flowise
Versions from 2.2.4 to 3.1.4 are in range. Then check whether the instance is reachable without a login. From a trusted network, confirm the API only answers through your reverse proxy or VPN and not on a public address.
Look in access logs for POST requests to the download path that came from addresses you do not recognize.
Because no fixed version is confirmed, the real decision is between a patched fork, a compensating control, or migration. free in-browser dependency scan lists known vulnerabilities for the flowise package in a manifest so you can track it.
What to do now
- Check your Flowise version with npm ls flowise.
- Put Flowise behind a VPN or an authenticating reverse proxy that blocks the download route for unauthenticated users.
- Review logs for requests to the openai-assistants-file/download route.
- Check whether a fork or newer release has fixed this CVE, and read its notes.
- Plan a migration or a maintained fork, since upstream is winding down.
Why it matters
CWE-862 here comes from a whitelist. Authentication whitelists exist for login pages and webhooks, and each entry is a hole by design. When a route that serves private files lands on that list, the whole access model is skipped.
The identifiers an attacker needs are not secrets in the usual sense. They appear in URLs and chat sessions. The lesson reaches beyond Flowise: protect file download routes with the same authorization as the objects they serve.
Quick check
Is upgrading to 3.1.3 enough?
No. The affected range runs to 3.1.4, so 3.1.3 does not cover this CVE. I could not confirm a fixed version, so use compensating controls and check for a fork or release that names it.
Sources
Last reviewed: 18 October 2026.
