Is CVE-2025-61913 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-61913 being exploited in the wild.

How severe is CVE-2025-61913?

Critical severity, with a CVSS score of 9.9, published 8 October 2025.

Which products and versions are affected?

flowise (npm) SEMVER:introduced=0,fixed=3.0.8; flowise-components (npm) SEMVER:introduced=0,fixed=3.0.8.

Is there a fix for CVE-2025-61913?

Yes. flowise (npm): upgrade to 3.0.8 or later; flowise-components (npm): upgrade to 3.0.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-61913 attacked?

It is attacked over the network.

Am I affected by CVE-2025-61913?

Check whether you run FlowiseAI Flowise, flowise (npm) or flowise-components (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-61913: Flowise WriteFileTool arbitrary file write vulnerability

CVE-2025-61913 · Severity: critical · CVSS 9.9 · Published 2025-10-08

Flowise is a low-code platform for building AI agent workflows that allows users to define automation tasks using a visual interface. The WriteFileTool component fails to validate file paths, allowing authenticated users to write arbitrary files anywhere on the server filesystem. This could lead to remote command execution by overwriting system configuration files, SSH keys, or application startup scripts.

Technologies: FlowiseAI Flowise, flowise (npm), flowise-components (npm). Vendors: FlowiseAI, npm.

Quick answers

Is CVE-2025-61913 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-61913 being exploited in the wild.
How severe is CVE-2025-61913?: Critical severity, with a CVSS score of 9.9, published 8 October 2025.
Which products and versions are affected?: flowise (npm) SEMVER:introduced=0,fixed=3.0.8; flowise-components (npm) SEMVER:introduced=0,fixed=3.0.8.
Is there a fix for CVE-2025-61913?: Yes. flowise (npm): upgrade to 3.0.8 or later; flowise-components (npm): upgrade to 3.0.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-61913 attacked?: It is attacked over the network.
Am I affected by CVE-2025-61913?: Check whether you run FlowiseAI Flowise, flowise (npm) or flowise-components (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

flowise (npm): upgrade to 3.0.8 or later
```
npm install flowise@3.0.8
```
flowise-components (npm): upgrade to 3.0.8 or later
```
npm install flowise-components@3.0.8
```

Technical details

The WriteFileTool in Flowise (packages/components/nodes/tools/WriteFile/WriteFile.ts) implements a file-writing function that accepts a user-supplied file_path parameter without validation or sandboxing checks. Authenticated attackers can exploit this to write files to arbitrary locations on the filesystem. Common attack vectors include writing SSH public keys to ~/.ssh/authorized_keys for remote access, modifying /etc/ld.so.preload for library hijacking, or overwriting package.json startup commands. The vulnerability requires authentication (user registration) but operates over the network with no additional user interaction. Patches are available in Flowise 3.0.8 and later.

Affected products

Flowise Flowise <=3.0.5

Identifiers

CVE-2025-61913
GHSA-jv9m-vf54-chjj

Timeline

2025-10-09: disclosed: Advisory GHSA-jv9m-vf54-chjj published
2025-10: patched: Fix available in Flowise 3.0.8

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.