Authenticated arbitrary file access via unrestricted tool paths
Published Oct 8, 2025 · Updated Oct 8, 2025
Path traversal in Flowise before 3.0.8 allows remote authenticated users to read and write arbitrary server files through file tools. ReadFileTool and WriteFileTool pass attacker-controlled file_path values directly to filesystem stores without verifying that the resolved path remains inside the Flowise workspace. A registered account and an agent flow that invokes a tool are required; reads expose secrets, while writes can replace executable files and achieve code execution.
Summary
What happened
Path traversal in Flowise before 3.0.8 allows remote authenticated users to read and write arbitrary server files through file tools. ReadFileTool and WriteFileTool pass attacker-controlled file_path values directly to filesystem stores without verifying that the resolved path remains inside the Flowise workspace. A registered account and an agent flow that invokes a tool are required; reads expose secrets, while writes can replace executable files and achieve code execution.
The record
- CVE
- CVE-2025-61913
- Published
- Oct 8, 2025
- Updated
- Oct 8, 2025
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- CWE-22, T1190, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 8, 2025CVE publishedPublication date reported by the CVE source.
- Oct 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.0.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- ReadFileTool Docker reproductionproof of concept · demonstrated
- WriteFileTool Docker reproductionproof of concept · demonstrated
- Chromium wrapper overwrite RCE chainfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo