Is CVE-2026-70476 exploited in the wild?

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

How severe is CVE-2026-70476?

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

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

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

Am I affected by CVE-2026-70476?

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-70476: Flowise broken access control in Stripe subscription endpoints

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

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

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

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

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

Flowise, an open-source tool for building LLM applications, contains a flaw in how it handles billing and subscription updates. An attacker with a valid account can modify the Stripe subscription details of other organizations by providing a victim's subscription ID. This could lead to unauthorized charges, service downgrades, or financial disruption for affected customers.

Technologies: flowise (npm). Vendors: npm.

Quick answers

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

Flowise suffers from an Insecure Direct Object Reference (IDOR) / Broken Access Control vulnerability in the `update-additional-seats` and `update-subscription-plan` routes within `organization.route.ts`. The server accepts a `subscriptionId` directly from the request body and processes billing changes via the Stripe integration without verifying if the subscription belongs to the authenticated user's organization. An attacker can obtain a victim's `subscriptionId` through other API endpoints and then issue POST requests to modify seat quantities or change subscription plans. This issue is fixed in version 3.1.3.

Affected products

FlowiseAI flowise <= 3.1.2

Identifiers

CVE-2026-70476
GHSA-gmmw-qg98-6j6p

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.