CVE-2026-56272: Flowise Insufficient Password Salt Rounds
Flowise
Flowise uses an insufficient default number of bcrypt salt rounds, lowering the cost of brute-force attacks against stored password hashes. Users are advised to update their configuration or patch.
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
- 5.6
- EPSS
- <0.01 · top 100% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 5 Mar 2026
- last update
- 24 Jun 2026
- CVE ids
Timeline · 2
Sources · 2
Advisories and databases
- 2026-03-05CVE-2026-56272: Flowise has Insufficient Password Salt RoundsGitHub Advisory Database · github.com/advisories/GHSA-x2g5-fvc2-gqvp
- 2026-06-24CVE-2026-56272: Flowise before 3.0.13 uses bcrypt with default salt rounds of 5, providing only 32 iterations instead of the OWASP-recommended…NVD · nvd.nist.gov/vuln/detail/CVE-2026-56272
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 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: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
# CVE-2026-56272: Flowise Insufficient Password Salt Rounds https://gcdradar.vercel.app/incidents/cve-2026-56272-flowise-insufficient-password-salt-rounds · AIR-2026-0490 · 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 - CVE ids: CVE-2026-56272 - CVSS: 5.6 ## Summary Flowise uses an insufficient default number of bcrypt salt rounds, lowering the cost of brute-force attacks against stored password hashes. Users are advised to update their configuration or patch. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-06-24: CVE-2026-56272: Flowise before 3.0.13 uses bcrypt with default salt rounds of 5, providing only 32 iterations instead of the OWASP-recommended… (https://nvd.nist.gov/vuln/detail/CVE-2026-56272) - 2026-03-05: CVE-2026-56272: Flowise has Insufficient Password Salt Rounds (https://github.com/advisories/GHSA-x2g5-fvc2-gqvp) ## Sources - 2026-03-05 GitHub Advisory Database: CVE-2026-56272: Flowise has Insufficient Password Salt Rounds https://github.com/advisories/GHSA-x2g5-fvc2-gqvp - 2026-06-24 NVD: CVE-2026-56272: Flowise before 3.0.13 uses bcrypt with default salt rounds of 5, providing only 32 iterations instead of the OWASP-recommended… https://nvd.nist.gov/vuln/detail/CVE-2026-56272 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed7.1Flowise CVE-2026-31829: Flowise Affected by Server-Side Request Forgery in HTTP Node
Patch now · Disclosed · since 11 Mar 2026 · updated 11 Mar 2026 · CVE-2026-31829
AI - closed7.7Flowise CVE-2026-30824: Flowise Missing Authentication on NVIDIA NIM Endpoints
Patch now · Disclosed · since 6 Mar 2026 · updated 7 Mar 2026 · CVE-2026-30824
AI - closed8.2Flowise CVE-2026-30821: Flowise Arbitrary File Upload via MIME Spoofing
Patch now · Disclosed · since 6 Mar 2026 · updated 7 Mar 2026 · CVE-2026-30821
AI - closed8.8Flowise CVE-2026-30823: Flowise IDOR and SSO Configuration Vulnerability
Patch now · Disclosed · since 6 Mar 2026 · updated 7 Mar 2026 · CVE-2026-30823
AI - closed8.7Flowise CVE-2026-30820: Flowise Authorization Bypass via Spoofed Header
Patch now · Disclosed · since 6 Mar 2026 · updated 7 Mar 2026 · CVE-2026-30820
AI - closed7.7Flowise CVE-2026-30822: Flowise Allows Mass Assignment on Leads Endpoint
Patch now · Disclosed · since 6 Mar 2026 · updated 7 Mar 2026 · CVE-2026-30822
AI