Flowise IDOR vulnerability exposes payment and profile data
Flowise
An insecure direct object reference vulnerability exists in Flowise allowing attackers to retrieve sensitive customer payment information. The flaw bypasses authorization checks through the customerId parameter.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- fix status
- Fix status unknown
- first report
- 4 Aug 2026
- last update
- 4 Aug 2026
Timeline · 1
Sources · 1
Advisories and databases
- 2026-08-04GHSA-2364-jh4q-m9vm: Flowise: IDOR vulnerability exists at the GET /api/v1/organization/customer-default-source endpointGitHub Advisory Database · github.com/advisories/GHSA-2364-jh4q-m9vm
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- dates
- happened 4 Aug 2026 · first reported 4 Aug 2026
- origin
- GitHub Advisory DatabaseVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 07:00Z · updated 2026-10-18 07:00Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# Flowise IDOR vulnerability exposes payment and profile data https://gcdradar.vercel.app/incidents/flowise-idor-vulnerability-exposes-payment-and-profile-data · AIR-2026-0879 · closed 2026-08-04 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2026-08-04 - AI role: Attack on AI - Products: Flowise ## Summary An insecure direct object reference vulnerability exists in Flowise allowing attackers to retrieve sensitive customer payment information. The flaw bypasses authorization checks through the customerId parameter. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-08-04: GHSA-2364-jh4q-m9vm: Flowise: IDOR vulnerability exists at the GET /api/v1/organization/customer-default-source endpoint (https://github.com/advisories/GHSA-2364-jh4q-m9vm) ## Sources - 2026-08-04 GitHub Advisory Database: GHSA-2364-jh4q-m9vm: Flowise: IDOR vulnerability exists at the GET /api/v1/organization/customer-default-source endpoint https://github.com/advisories/GHSA-2364-jh4q-m9vm Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed8.6Flowise CVE-2026-73484: Flowise pythonCodeValidator sandbox escape vulnerability
Patch now · Disclosed · since 13 Aug 2026 · CVE-2026-73484
AI - closed6.3Flowise CVE-2026-73603: Chatflow visibility bypass in Flowise TTS endpoint
Patch now · Disclosed · since 13 Aug 2026 · CVE-2026-73603
AI - closed9.0Flowise CVE-2026-73486: Code injection in Flowise CSV Agent node
Patch now · Disclosed · since 13 Aug 2026 · CVE-2026-73486
AI - closed7.1Flowise CVE-2026-73604: Incomplete credential redaction in Flowise API
Patch now · Disclosed · since 13 Aug 2026 · CVE-2026-73604
AI - closed9.9Flowise CVE-2026-73602: Sandbox escape and code execution in Flowise
Patch now · Disclosed · since 13 Aug 2026 · CVE-2026-73602
AI - closed9.0Flowise CVE-2026-73601: Remote code execution in Flowise Custom MCP node
Patch now · Disclosed · since 13 Aug 2026 · CVE-2026-73601
AI