Is CVE-2026-70475 exploited in the wild?

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

How severe is CVE-2026-70475?

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

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

It is attacked over the network, in a software library.

Am I affected by CVE-2026-70475?

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-70475: Flowise missing authorization in execution update endpoint

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

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

It is attacked over the network, in a software library.

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

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

Flowise, an open-source tool for building LLM-based workflows, contains a security flaw in how it handles workflow execution updates. An authenticated user with low-level access can bypass intended restrictions to modify the state or data of any execution record within their workspace. This could allow an attacker to manipulate workflow results or inject unauthorized data into the system.

Technologies: flowise (npm). Vendors: npm.

Quick answers

Is CVE-2026-70475 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-70475 being exploited in the wild.
How severe is CVE-2026-70475?: 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-70475?: 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-70475 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-70475?: 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

A missing authorization vulnerability (CWE-862) exists in Flowise versions up to 3.1.2. The 'PUT /api/v1/executions/:id' endpoint fails to implement the 'checkAnyPermission()' middleware, which is correctly applied to GET and DELETE operations in the same route file. An attacker with a valid low-privileged API key can exploit this to modify the state, data, and metadata of any execution record. This vulnerability was addressed in version 3.1.3 by adding the appropriate permission checks to the update route.

Affected products

FlowiseAI flowise <= 3.1.2

Identifiers

CVE-2026-70475
GHSA-fm2f-4339-4p2f

Timeline

2026-03-17: disclosed: Vulnerability discovered by researcher Dimpal Jadhav
2026-07-29: patched: Fix released in version 3.1.3
2026-08-04: advisory: GitHub Advisory published

References

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