Is CVE-2026-56273 exploited in the wild?

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

How severe is CVE-2026-56273?

Medium severity, with a CVSS score of 6.5, published 8 July 2026.

Which products and versions are affected?

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

Is there a fix for CVE-2026-56273?

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

How is CVE-2026-56273 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-56273?

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.

CVE-2026-56273: Flowise path traversal in Faiss and SimpleStore vector stores

CVE-2026-56273 · Severity: medium · CVSS 6.5 · Published 2026-07-08

Flowise, an open-source tool for building LLM applications, is vulnerable to a security flaw in how it handles file paths for data storage. An authenticated user with a valid API token can bypass directory restrictions to write data to unauthorized locations on the server's filesystem. This could allow an attacker to overwrite critical system files, potentially leading to full system takeover or data theft.

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

Quick answers

Is CVE-2026-56273 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-56273 being exploited in the wild.
How severe is CVE-2026-56273?: Medium severity, with a CVSS score of 6.5, published 8 July 2026.
Which products and versions are affected?: flowise (npm) SEMVER:introduced=0,fixed=3.1.0; flowise-components (npm) SEMVER:introduced=0,fixed=3.1.0.
Is there a fix for CVE-2026-56273?: Yes. flowise (npm): upgrade to 3.1.0 or later; flowise-components (npm): upgrade to 3.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-56273 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-56273?: 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.0 or later
```
npm install flowise@3.1.0
```
flowise-components (npm): upgrade to 3.1.0 or later
```
npm install flowise-components@3.1.0
```

Technical details

A path traversal vulnerability (CWE-22) exists in Flowise versions prior to 3.1.0 within the Faiss and SimpleStore (LlamaIndex) vector store components. The root cause is the lack of sanitization for the 'basePath' parameter in the 'upsert' function of Faiss.ts and SimpleStore.ts, which is passed directly to filesystem write operations. An authenticated attacker with 'documentStores:upsert-config' permissions and a valid API token can provide a manipulated path (e.g., using '../' sequences) to write vector store data to arbitrary locations. This can result in overwriting sensitive files, achieving remote code execution by targeting web-accessible directories, or exfiltrating data via network-mounted drives. The issue is resolved in version 3.1.0.

Affected products

FlowiseAI Flowise < 3.1.0
FlowiseAI flowise-components < 3.1.0

Identifiers

CVE-2026-56273
GHSA-w6v6-49gh-mc9w

Timeline

2026-04-15: advisory: GitHub Security Advisory published
2026-07-08: disclosed: NVD publication date

References

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