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?

Medium severity, with a CVSS score of 4, published 4 August 2026.

Which products and versions are affected?

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

Is there a fix for This vulnerability?

Yes. flowise (npm): upgrade to 3.1.3 or later; flowise-components (npm): upgrade to 3.1.3 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, in a software library.

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.

Flowise arbitrary file write in S3 Directory document loader

Severity: medium · CVSS 4 · Published 2026-08-04

Flowise is an open-source low-code platform for building AI applications. The S3 Directory document loader contains a path-traversal vulnerability that allows authenticated users with a specific role to write files to arbitrary locations on the server. An attacker can exploit this to overwrite application data, configuration files, or secrets, and potentially achieve remote code execution if the Flowise process has write access to executable or startup files.

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

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?: Medium severity, with a CVSS score of 4, published 4 August 2026.
Which products and versions are affected?: flowise (npm) SEMVER:introduced=0,fixed=3.1.3; flowise-components (npm) SEMVER:introduced=0,fixed=3.1.3.
Is there a fix for This vulnerability?: Yes. flowise (npm): upgrade to 3.1.3 or later; flowise-components (npm): upgrade to 3.1.3 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, in a software library.
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.1.3 or later
```
npm install flowise@3.1.3
```
flowise-components (npm): upgrade to 3.1.3 or later
```
npm install flowise-components@3.1.3
```

Technical details

The vulnerability is a path-traversal flaw (CWE-22) in the S3 Directory document loader. When processing S3 object keys, the loader uses path.join(tempDir, key) without validating that the key contains traversal sequences (e.g., ../). The resolved path is then used to create directories and write files with no validation that the destination remains within the intended temporary directory. An authenticated attacker with the documentStores:preview-process role can craft S3 object keys containing path traversal sequences and point the loader to an attacker-controlled S3-compatible endpoint (e.g., MinIO) to write arbitrary files to any path writable by the Flowise process. The temporary directory cleanup removes only the original temp directory, leaving escaped files persisted on disk. A related variant exists in the S3File loader. No user interaction is required beyond initial authentication.

Affected products

FlowiseAI Flowise <=3.1.2
FlowiseAI flowise-components <=3.1.2

Timeline

2026-08-04: disclosed
2026-08-04: patched: Version 3.1.3 released with fix

References

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