Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Low severity, with a CVSS score of 3.1, published 10 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 This vulnerability?
- 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 This vulnerability attacked?
- It is attacked over the network.
- Am I affected?
- Check whether you run 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 vulnerability is a path traversal / arbitrary file read in the ReadFileTool component (packages/components/nodes/tools/ReadFile/ReadFile.ts). The tool accepts a user-supplied file_path parameter and passes it directly to the underlying file store without validating whether the path is within an allowed directory. An authenticated attacker can exploit this to read sensitive files such as /root/.flowise/encryption.key, /root/.flowise/database.sqlite, /etc/passwd, /etc/shadow, and SSH keys. The vulnerability requires authentication (attackers must register an account first) but no additional user interaction. The fix is available in version 3.0.8 and later.
Affected products
- Flowise Flowise <=3.0.5
Timeline
- 2025-10-08: disclosed
- 2025-10-08: patched: Version 3.0.8 and later patch the vulnerability