Is CVE-2026-70472 exploited in the wild?

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

How severe is CVE-2026-70472?

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

Which products and versions are affected?

flowise (npm) <= 3.1.2, SEMVER:introduced=0,fixed=3.1.3.

Is there a fix for CVE-2026-70472?

Yes. flowise (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 CVE-2026-70472 attacked?

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

Am I affected by CVE-2026-70472?

Check whether you run flowise (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-70472: Flowise IDOR in openai-assistants-vector-store

Q: Which products and versions are affected?

flowise (npm) <= 3.1.2, SEMVER:introduced=0,fixed=3.1.3.

Q: Is there a fix for CVE-2026-70472?

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

Q: How is CVE-2026-70472 attacked?

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

Q: Am I affected by CVE-2026-70472?

Check whether you run flowise (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-70472 · Severity: high · CVSS 8.8 · Published 2026-08-04

Flowise, an open-source tool for building LLM applications, is vulnerable to an authorization flaw that allows users in one workspace to access credentials belonging to another workspace. By providing a specific ID, an attacker can use a victim's OpenAI API keys, leading to unauthorized data access and unexpected billing charges on the victim's account. This compromises the security boundaries between different teams or customers using the same Flowise instance.

Technologies: flowise (npm). Vendors: npm.

Quick answers

Is CVE-2026-70472 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-70472 being exploited in the wild.
How severe is CVE-2026-70472?: High severity, with a CVSS score of 8.8, published 4 August 2026.
Which products and versions are affected?: flowise (npm) <= 3.1.2, SEMVER:introduced=0,fixed=3.1.3.
Is there a fix for CVE-2026-70472?: Yes. flowise (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 CVE-2026-70472 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-70472?: Check whether you run flowise (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
```

Technical details

An Insecure Direct Object Reference (IDOR) exists in Flowise versions 3.1.2 and earlier within the `openai-assistants-vector-store` component. The application fails to validate workspace ownership when loading credentials via the `credential` parameter in API requests. An authenticated attacker can supply a `credentialId` belonging to a different workspace to the `/api/v1/openai-assistants-vector-store` endpoint. The server then retrieves and uses the associated OpenAI API key without verifying if the caller has permission to access that specific workspace's resources. This allows for unauthorized read/modify/delete operations on vector stores and files, as well as unauthorized use of the victim's OpenAI quota. The issue is fixed in version 3.1.3.

Affected products

FlowiseAI Flowise <= 3.1.2

Identifiers

CVE-2026-70472
GHSA-chm3-vqcf-52rx

Timeline

2026-07-29: patched: Fixed in version 3.1.3
2026-08-04: disclosed: GitHub Advisory published

References

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