Skip to main content
CVE-2025-61687VulnerabilityPublished

CVE-2025-61687: FlowiseAI Flowise · Unrestricted File Upload

Affects FlowiseAI FlowiseSource CVE Database V5

0

Not known to be exploited · 10% EPSS · CVSS 8.3 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
10.9% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
FlowiseAI FlowiseAffected
  • =3.0.7
Fixed in–

AI-suggested

1. Immediately restrict access to Flowise 3.0.7 instances to trusted users only and enforce strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of unauthorized uploads. 2. Implement strict network segmentation and firewall rules to limit external and internal access to the Flowise server, minimizing exposure. 3. Monitor file upload directories for unexpected or suspicious files, especially those with Node.js extensions or unusual content, and establish automated alerts for such anomalies. 4. Conduct regular audits of uploaded files and server filesystem integrity to detect and remove any malicious shells promptly. 5. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious HTTP requests targeting potential web shell endpoints. 6. If possible, temporarily disable file upload functionality or restrict allowed file types to a safe whitelist until an official patch is released. 7. Keep all related software and dependencies updated and subscribe to vendor advisories for timely patching once available. 8. Educate administrators and users about the risks of this vulnerability and the importance of cautious handling of uploaded files and credentials. 9. Consider deploying endpoint detection and response (EDR) solutions to identify unusual command executions or lateral movement attempts stemming from this vulnerability.

Description

Flowise is a drag & drop user interface to build a customized large language model flow. A file upload vulnerability in version 3.0.7 of FlowiseAI allows authenticated users to upload arbitrary files without proper validation. This enables attackers to persistently store malicious Node.js web shells on the server, potentially leading to Remote Code Execution (RCE). The system fails to validate file extensions, MIME types, or file content during uploads. As a result, malicious scripts such as Node.js-based web shells can be uploaded and stored persistently on the server. These shells expose HTTP endpoints capable of executing arbitrary commands if triggered. The uploaded shell does not automatically execute, but its presence allows future exploitation via administrator error or chained vulnerabilities. This presents a high-severity threat to system integrity and confidentiality. As of time of publication, no known patched versions are available.

References

Community reviews

Loading reviews…