Skip to content
Fencer Intel
critical 10.0

CVE-2025-61913 in the critical feed json

Flowise is vulnerable to arbitrary file read, arbitrary file write

published last yr. modified last mo. also EUVD-2025-33322 , GHSA-jv9m-vf54-chjj

cvss
10.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
13.9%
EPSS 13.9% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm flowise 3.0.8
  • npm flowise-components 3.0.8
  • npm Flowise 3.0.8
  • flowiseai flowise 3.0.8

Is CVE-2025-61913 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 Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

13.87% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-jv9m-vf54-chjj referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-j44m-5v8f-gc9c referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm flowise
<3.0.8
3.0.8
npm flowise-components
<3.0.8
3.0.8
npm Flowise
<3.0.8
3.0.8

Affected products

  • FlowiseAI Flowise

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.