Is CVE-2026-70473 exploited in the wild?

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

How severe is CVE-2026-70473?

High severity, with a CVSS score of 8.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-70473?

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

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

Am I affected by CVE-2026-70473?

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-70473: Flowise information disclosure in upsert-history API

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

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

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

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

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

Flowise, an open-source tool for building LLM applications, contains a vulnerability where a specific interface returns the entire server's history to any logged-in user. This allows an attacker to view sensitive configuration details and infrastructure information belonging to other users or organizations. Such exposure could lead to targeted attacks on a company's data storage or cause service performance issues due to the massive size of the data being transferred.

Technologies: flowise (npm). Vendors: npm.

Quick answers

Is CVE-2026-70473 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-70473 being exploited in the wild.
How severe is CVE-2026-70473?: High severity, with a CVSS score of 8.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-70473?: 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-70473 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-70473?: 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 information disclosure vulnerability exists in Flowise due to missing authorization and data scoping in the 'GET /api/v1/upsert-history' endpoint. The root cause is a failure to restrict query results to the requesting user's tenant or workspace, causing the server to return the entire global upsert history. A remote attacker with low privileges (authenticated user) can exploit this by sending a simple GET request to the affected endpoint. The resulting response can exceed 100MB and contains sensitive infrastructure details, including Vector Store URLs, collection names, and integration parameters. This issue is patched in version 3.1.3.

Affected products

FlowiseAI flowise <= 3.1.2

Identifiers

CVE-2026-70473
GHSA-fr6g-7cq8-fg82

Timeline

2026-07-29: disclosed: Initial disclosure to vendor
2026-08-04: advisory: GitHub Advisory published
2026-08-04: patched: Version 3.1.3 released

References

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