Is CVE-2026-73488 exploited in the wild?

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

How severe is CVE-2026-73488?

Medium severity, with a CVSS score of 6.5, published 13 August 2026.

Which products and versions are affected?

flowise (npm) SEMVER:introduced=0,fixed=3.1.3.

Is there a fix for CVE-2026-73488?

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

It is attacked over the network, in a web application.

Am I affected by CVE-2026-73488?

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-73488: Flowise IDOR in payment source endpoint

CVE-2026-73488 · Severity: medium · CVSS 6.5 · Published 2026-08-13

Flowise is an open-source platform for building AI agents visually. A broken access control flaw in its payment source endpoint allows any authenticated user to retrieve sensitive billing and profile information (email addresses, account balances, payment methods) belonging to other customers by manipulating a customer ID parameter. This exposure could lead to identity theft, account takeover, and regulatory violations under data protection laws like GDPR.

Technologies: flowise (npm). Vendors: npm.

Quick answers

Is CVE-2026-73488 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-73488 being exploited in the wild.
How severe is CVE-2026-73488?: Medium severity, with a CVSS score of 6.5, published 13 August 2026.
Which products and versions are affected?: flowise (npm) SEMVER:introduced=0,fixed=3.1.3.
Is there a fix for CVE-2026-73488?: 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-73488 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-73488?: 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 is a broken access control (CWE-639) flaw at the GET /api/v1/organization/customer-default-source endpoint. While the endpoint enforces authentication (requires a valid session token), it fails to verify object-level authorization—it does not check whether the requesting user owns or has permission to access the requested customerId. An authenticated attacker can craft requests with customer IDs in a predictable Stripe-formatted pattern (cus_XXXX) to enumerate and retrieve PII and financial data. The attack requires only network access and a valid account; no additional user interaction is needed. The vulnerability was patched in version 3.1.3 by implementing proper ownership validation on the customerId parameter, as shown in commit 4d7899d02ca370a5510406be5c91483085a412f9.

Affected products

FlowiseAI Flowise prior to 3.1.3

Identifiers

CVE-2026-73488
GHSA-2364-jh4q-m9vm

Timeline

2026-07-27: disclosed
2026-06-25: patched: Fix released in version 3.1.3
2026-08-04: advisory

References

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