Is CVE-2026-70474 exploited in the wild?

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

How severe is CVE-2026-70474?

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

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

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

Am I affected by CVE-2026-70474?

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-70474: Flowise OAuth2 credential isolation bypass and authentication bypass

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

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

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

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

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

Flowise, a tool used for building LLM applications, contains a vulnerability in how it handles OAuth2 credentials across different workspaces. An attacker can exploit this to steal sensitive access tokens for third-party services (like Google or Microsoft) or overwrite existing credentials without needing to log in. This could lead to unauthorized access to corporate data stored in connected services and disrupt automated workflows.

Technologies: flowise (npm). Vendors: npm.

Quick answers

Is CVE-2026-70474 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-70474 being exploited in the wild.
How severe is CVE-2026-70474?: High severity, with a CVSS score of 8.1, 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-70474?: 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-70474 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-70474?: 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 vulnerability exists in the OAuth2 credential management routes within `packages/server/src/routes/oauth2/index.ts`. The `authorize`, `callback`, and `refresh` endpoints perform database lookups for credentials using only the `id` (UUID) without verifying the `workspaceId`. Furthermore, the `callback` and `refresh` endpoints are explicitly whitelisted from authentication in `packages/server/src/utils/constants.ts`. An unauthenticated attacker with knowledge of a credential UUID can trigger a token refresh to obtain a valid `access_token` in the response body, or forge a callback to inject malicious tokens. Authenticated users can also leak metadata (client IDs and scopes) from credentials belonging to other workspaces. The issue is resolved in version 3.1.3 by enforcing workspace scoping and removing the authentication bypass.

Affected products

FlowiseAI Flowise <= 3.1.2

Identifiers

CVE-2026-70474
GHSA-wch5-xp77-fxg4

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.