Flowise API response handler exposes bcrypt password hashes
Flowise
An information disclosure vulnerability exists in Flowise authentication components up to version 3.0.12. Remote attackers could potentially exploit the flaw to view sensitive password hash data.
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
- CVSS
- 6.3
- EPSS
- <0.01 · top 83% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 6 May 2026
- last update
- 6 May 2026
- CVE ids
Timeline · 2
Sources · 2
Advisories and databases
- 2026-05-06CVE-2026-8026: Flowise: Bcrypt Password Hash ExposureGitHub Advisory Database · github.com/advisories/GHSA-8f47-4rh3-x44m
- 2026-05-06CVE-2026-8026: A security flaw has been discovered in FlowiseAI Flowise up to 3.0.12.NVD · nvd.nist.gov/vuln/detail/CVE-2026-8026
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 6 May 2026 · first reported 6 May 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:04Z
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 API response handler exposes bcrypt password hashes https://gcdradar.vercel.app/incidents/flowise-api-response-handler-exposes-bcrypt-password-hashes · AIR-2026-0620 · closed 2026-05-06 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2026-05-06 - AI role: Attack on AI - Products: Flowise - CVE ids: CVE-2026-8026 - CVSS: 6.3 ## Summary An information disclosure vulnerability exists in Flowise authentication components up to version 3.0.12. Remote attackers could potentially exploit the flaw to view sensitive password hash data. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-05-06: CVE-2026-8026: A security flaw has been discovered in FlowiseAI Flowise up to 3.0.12. (https://nvd.nist.gov/vuln/detail/CVE-2026-8026) - 2026-05-06: CVE-2026-8026: Flowise: Bcrypt Password Hash Exposure (https://github.com/advisories/GHSA-8f47-4rh3-x44m) ## Sources - 2026-05-06 GitHub Advisory Database: CVE-2026-8026: Flowise: Bcrypt Password Hash Exposure https://github.com/advisories/GHSA-8f47-4rh3-x44m - 2026-05-06 NVD: CVE-2026-8026: A security flaw has been discovered in FlowiseAI Flowise up to 3.0.12. https://nvd.nist.gov/vuln/detail/CVE-2026-8026 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- 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 - closedFlowise Flowise hardcoded CORS wildcard on TTS endpoint
Patch now · Disclosed · since 20 May 2026
AI - closedFlowise Flowise mass assignment password override vulnerability
Patch now · Disclosed · since 20 May 2026
AI - closedFlowise Flowise MCP security bypass leads to RCE
Patch now · Disclosed · since 14 May 2026
AI - closed5.3Flowise CVE-2026-8027: Authorization bypass in FlowiseAI Flowise user controller handler
Patch now · Disclosed · since 6 May 2026 · CVE-2026-8027
AI - closed3.7Flowise CVE-2026-8028: Information disclosure vulnerability in FlowiseAI Flowise
Patch now · Disclosed · since 6 May 2026 · CVE-2026-8028
AI