Is CVE-2026-70478 exploited in the wild?

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

How severe is CVE-2026-70478?

Critical severity, with a CVSS score of 10, 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-70478?

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

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

Am I affected by CVE-2026-70478?

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-70478: Flowise unauthenticated OAuth2 token refresh in credential 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-70478?

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

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

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

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-70478 · Severity: critical · CVSS 10 · Published 2026-08-04

Flowise, an open-source tool for building LLM applications, contains a security flaw in how it handles third-party service connections like Google, Microsoft, and GitHub. An unauthorized attacker can remotely request a new access token for these connected services without providing any credentials. If successful, this allows the attacker to take over the victim's connected accounts and access their private data.

Technologies: flowise (npm). Vendors: npm.

Quick answers

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

The OAuth2 token refresh endpoint (POST /api/v1/oauth2-credential/refresh/:credentialId) was incorrectly included in the WHITELIST_URLS constant, bypassing authentication requirements. When called with a valid credential ID, the server decrypts the stored OAuth2 credentials, performs a refresh request to the provider, and returns the resulting access_token directly in the JSON response. Attackers can obtain credential IDs through enumeration or other information leaks to gain full access to a victim's connected third-party accounts. This vulnerability is patched in version 3.1.3.

Affected products

FlowiseAI flowise <= 3.1.2

Identifiers

CVE-2026-70478
GHSA-qgvm-j2hm-6m38

Timeline

2026-07-29: disclosed
2026-08-04: advisory
2026-08-04: patched

References

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