Skip to main content
CVE-2025-61913VulnerabilityPublished Updated

CVE-2025-61913: FlowiseAI Flowise · Path Traversal

Affects FlowiseAI FlowiseSource CVE Database V5

0

Not known to be exploited · 12% EPSS · CVSS 10.0 Critical : upgrade to 3.0.8 as a priority.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
12.9% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.0.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 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

Upgrade FlowiseAI Flowise to 3.0.8.

Affected software

ProductAffectedFixed in
FlowiseAI FlowiseAffected
  • <3.0.8
Fixed in
  • 3.0.8

AI-suggested

1. Immediate upgrade to Flowise version 3.0.8 or later, which contains the patch restricting file path access. 2. Implement strict authentication and authorization controls to limit access to Flowise tools only to trusted users. 3. Employ application-level input validation and sanitization to detect and block path traversal attempts. 4. Monitor file system access logs for unusual read/write activity, especially outside expected directories. 5. Use network segmentation to isolate Flowise instances from critical infrastructure to limit lateral movement. 6. Conduct regular security audits and penetration testing focusing on AI workflow tools. 7. Apply the principle of least privilege to service accounts and users interacting with Flowise. 8. Maintain up-to-date backups to enable recovery in case of exploitation. 9. Educate developers and administrators on secure configuration and patch management for AI tools. 10. Consider deploying runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect exploitation attempts in real time.

Description

Flowise is a drag & drop user interface to build a customized large language model flow. In versions prior to 3.0.8, WriteFileTool and ReadFileTool in Flowise do not restrict file path access, allowing authenticated attackers to exploit this vulnerability to read and write arbitrary files to any path in the file system, potentially leading to remote command execution. Flowise 3.0.8 fixes this vulnerability.

References

Community reviews

Loading reviews…