Flowise Vulnerable to PII Disclosure
Flowise
An unauthenticated endpoint in Flowise exposes sensitive user object information in the response body. A patch has been issued.
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
- 5 Mar 2026
- last update
- 5 Mar 2026
Timeline · 1
Sources · 1
Advisories and databases
- 2026-03-05GHSA-jc5m-wrp2-qq38: Flowise Vulnerable to PII Disclosure on Unauthenticated Forgot Password EndpointGitHub Advisory Database · github.com/advisories/GHSA-jc5m-wrp2-qq38
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 vulnerabilityData leak
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- mitre atlas
- no technique for these categories
- dates
- happened 5 Mar 2026 · first reported 5 Mar 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 10:14Z
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 Vulnerable to PII Disclosure https://gcdradar.vercel.app/incidents/ghsa-jc5m-wrp2-qq38-flowise-vulnerable-to-pii-disclosure · AIR-2026-0491 · closed 2026-03-05 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2026-03-05 - AI role: Attack on AI - Products: Flowise ## Summary An unauthenticated endpoint in Flowise exposes sensitive user object information in the response body. A patch has been issued. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-03-05: GHSA-jc5m-wrp2-qq38: Flowise Vulnerable to PII Disclosure on Unauthenticated Forgot Password Endpoint (https://github.com/advisories/GHSA-jc5m-wrp2-qq38) ## Sources - 2026-03-05 GitHub Advisory Database: GHSA-jc5m-wrp2-qq38: Flowise Vulnerable to PII Disclosure on Unauthenticated Forgot Password Endpoint https://github.com/advisories/GHSA-jc5m-wrp2-qq38 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed7.1Flowise CVE-2026-73604: Incomplete credential redaction in Flowise API
Patch now · Disclosed · since 13 Aug 2026 · CVE-2026-73604
AI - closed8.7Flowise CVE-2026-71962: Flowise Missing Authorization on Assistant File Download
Patch now · Disclosed · since 10 Aug 2026 · CVE-2026-71962
AI - closed7.6Flowise CVE-2026-70474: Flowise Cross-Workspace OAuth2 Credential Metadata Leak
Patch now · Disclosed · since 4 Aug 2026 · CVE-2026-70474
AI - closed8.3Flowise CVE-2026-70473: Flowise Information Disclosure via Upsert History
Patch now · Disclosed · since 4 Aug 2026 · CVE-2026-70473
AI - closedFlowise Flowise incomplete credential redaction exposes secrets
Patch now · Disclosed · since 4 Aug 2026
AI - closed7.7Flowise CVE-2026-56268: Flowise cross-workspace chatflow information disclosure
Patch now · Disclosed · since 20 May 2026 · updated 22 Jun 2026 · CVE-2026-56268
AI