Is CVE-2026-70471 exploited in the wild?

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

How severe is CVE-2026-70471?

High severity, with a CVSS score of 6.5, 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-70471?

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-70471 attacked?

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

Am I affected by CVE-2026-70471?

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-70471: Flowise RBAC bypass in workspace variables injection

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-70471?

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-70471 attacked?

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

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

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-70471 · Severity: high · CVSS 6.5 · Published 2026-08-04

Flowise, an open-source tool for building LLM applications, contains a security flaw that allows users with limited access to view sensitive workspace secrets. By using specific custom functions, an attacker can bypass intended permission restrictions to access database passwords, API keys, and other credentials stored in the environment. This could lead to unauthorized access to connected third-party services and sensitive corporate data.

Technologies: flowise (npm). Vendors: npm.

Quick answers

Is CVE-2026-70471 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-70471 being exploited in the wild.
How severe is CVE-2026-70471?: High severity, with a CVSS score of 6.5, 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-70471?: 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-70471 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-70471?: 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 authorization bypass exists in Flowise due to improper Role-Based Access Control (RBAC) enforcement when handling workspace variables. While the official Variables API (/api/v1/variables) correctly enforces the 'variables:view' permission, the custom function endpoint (/api/v1/node-custom-function) fetches and injects the full '$vars' object into the execution sandbox without verifying this permission. This object contains both static workspace variables and runtime variables resolved from 'process.env'. An authenticated attacker with low privileges can exploit this by executing a custom function to leak sensitive information such as JWT secrets, SMTP passwords, and cloud provider keys. The vulnerability is addressed in version 3.1.3.

Affected products

FlowiseAI flowise <= 3.1.2

Identifiers

CVE-2026-70471
GHSA-8r8h-6vcc-xhrv

Timeline

2026-07-29: disclosed: Initial report to vendor
2026-08-04: advisory: GitHub Advisory published
2026-08-04: patched: Fixed in version 3.1.3

References

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