CVE-2025-71334 json
Flowise - Arbitrary File Access via Missing Chat Flow ID Validation
published last yr. modified 6d ago also GHSA-q67q-549q-p849 , EUVD-2025-210340
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.4%
- EPSS 4.4% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
Flowise before 3.0.6 contains an arbitrary file access vulnerability due to missing validation that the chatflowId and chatId parameters are UUIDs or numbers in file handling operations. By supplying a path-traversal value (e.g., '../../../../../tmp') as the chatflow id, an unauthenticated attacker can use the /api/v1/chatflows endpoint (via addBase64FilesToStorage) to write arbitrary files, and the /api/v1/get-upload-file and /api/v1/openai-assistants-file/download endpoints (via streamStorageFile) to read arbitrary files. Arbitrary file write may lead to remote code execution.
Patch / fix
- npm flowise 3.0.6
- Flowise Flowise 3.0.6
Is CVE-2025-71334 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 4mo ago
Exploit prediction
4.36% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template Flowise - Path Traversal nuclei detection template
- github.com https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-q67q-549q-p849 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 9.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | flowise | >=2.2.8, <3.0.6 |
3.0.6 |
Affected products
- Flowise Flowise
Classification
References
-
github.com
/FlowiseAI/Flowise/commit/8bd3de41533de78e4ef6c980e5704a1f9cb7ae6f
patch, web
-
github.com
/FlowiseAI/Flowise/commit/c2b830f279e454e8b758da441016b2234f220ac7
patch, web
-
github.com
/FlowiseAI/Flowise/security/advisories/GHSA-q67q-549q-p849
vendor-advisory, exploit, web
-
vulncheck.com
/advisories/flowise-arbitrary-file-access-via-missing-chat-flow-id-validation
third-party-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2025-71334
advisory
-
github.com
/FlowiseAI/Flowise
package
Sources
- CVE List CVE-2025-71334
- GitHub Advisory GHSA-q67q-549q-p849
- NVD CVE-2025-71334
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.