Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-71962 – Missing Authorization / Unauthenticated File Disclosure – Flowise 2.2.4 through 3.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-71962 is a missing authorization vulnerability (CWE-862) in FlowiseAI’s Flowise, the open-source low-code platform for building LLM apps and AI agents. The POST /api/v1/openai-assistants-file/download endpoint is globally whitelisted, allowing unauthenticated attackers to bypass session and API key verification and retrieve private files. It is rated High severity.

Technical details

  • Root cause: The POST /api/v1/openai-assistants-file/download endpoint was added to the global authentication whitelist, causing it to bypass all session and API key verification.
  • Trigger conditions: An attacker supplies valid chatflowId, chatId, and fileName identifiers to the endpoint; no credentials are required.
  • Attack vector: Network — the endpoint is reachable by unauthenticated remote attackers.
  • Impact: Unauthorized disclosure of private files from any chatflow, including files belonging to private chatflows in other workspaces or organizations. Confidentiality impact only; no integrity or availability impact reported.

Affected software

  • Flowise versions 2.2.4 through 3.1.4 (inclusive).

Severity

  • CVSS v3.1 base score: 7.5 (High) — vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
  • CVSS v4.0 base score: 8.7 (High) — 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.

Mitigation and recommended actions

  • Immediate: No fixed release has been published. FlowiseAI announced an end-of-life sunset: code freeze on July 29, 2026, repository archival and package/image deprecation on August 10, 2026, and end of core-team support on August 31, 2026. Organizations should plan migration away from Flowise or adopt a community-maintained fork that remediates this issue.
  • If no patch: Block or restrict network access to the POST /api/v1/openai-assistants-file/download endpoint using a reverse proxy, WAF, or firewall rules; place Flowise behind an authenticating gateway; and remove the endpoint from any unauthenticated exposure to the internet.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge