CVE-2025-71338: Flowise Contains a Path Traversal Vulnerability
Source GCVE Database
Not known to be exploited · CVSS 10.0 Critical.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
AI-suggested
Until a fix is available, restrict access to the vulnerable endpoint and validate or sanitize fileName inputs to prevent path traversal exploitation.
Description
Flowise has a critical path traversal vulnerability in the /api/v1/document-store/loader/process endpoint. This flaw allows unauthenticated attackers to write arbitrary files to the filesystem by exploiting unsanitized fileName parameters containing ../ sequences. Successful exploitation can overwrite important files such as package.json, potentially enabling remote code execution upon application restart.
References
- github.com/FlowiseAI/Flowise/security/advisories/GHSA-8vvx-qvq9-5948 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2025-71338 (opens in a new tab)
- vulncheck.com/advisories/flowise-arbitrary-file-write-to-remote-code-execution-via-document-store-api (opens in a new tab)
- github.com/FlowiseAI/Flowise/releases/tag/flowise%402.2.7-patch.1 (opens in a new tab)