CVE-2026-71962
Auth bypass in Flowise API allows unauthenticated download of private files.
Is CVE-2026-71962 being exploited?
Not confirmed. CVE-2026-71962 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.69% probability of exploitation in the next 30 days.
How severe is CVE-2026-71962?
CVE-2026-71962 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-71962?
Yes. A fix has been recorded for CVE-2026-71962. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-71962 affect?
CVE-2026-71962 affects Flowise 2.2.4 - 3.1.4, Self-hosted Flowise instances, Deployments exposing /api/v1/openai-assistants-file/download. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71962?
Block/require auth for the endpoint, remove it from global whitelist, restrict access, and patch when available.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can download arbitrary private chatflow files across workspaces by supplying chatflowId/chatId/fileName.
Immediate action required
- affected>= 2.2.4 and <= 3.1.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.