CVE-2026-73488Public exploitNetwork attack vector

Authenticated cross-customer data disclosure via unchecked customerId

Published Aug 13, 2026 · Updated Aug 13, 2026

IDOR in Flowise before 3.1.3 allows remote authenticated users to read other customers' payment and profile data through an API request. The GET /api/v1/organization/customer-default-source endpoint accepts customerId and returns the matching billing record after checking only for a valid session, without verifying ownership. Any registered user can enumerate predictable Stripe-style customer IDs; impact is limited to disclosure of email addresses, balances, currency, and billing settings.

CVSS severity6.0
Medium
EPSS probability0.32%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

IDOR in Flowise before 3.1.3 allows remote authenticated users to read other customers' payment and profile data through an API request. The GET /api/v1/organization/customer-default-source endpoint accepts customerId and returns the matching billing record after checking only for a valid session, without verifying ownership. Any registered user can enumerate predictable Stripe-style customer IDs; impact is limited to disclosure of email addresses, balances, currency, and billing settings.

The record

CVE
CVE-2026-73488
Published
Aug 13, 2026
Updated
Aug 13, 2026
Vendor
FlowiseAI
Product
Flowise
Classifications
CWE-639, T1213
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 13, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 13, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <3.1.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

FlowiseAI · Flowiseversion=0 <3.1.3

Published CVSS scores

6.0GitHubCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-639Authorization Bypass Through User-Controlled Key
T1213Data from Information Repositories

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo