EUVD-2026-38748Severity by source
CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Requires prior database extraction under high privilege (PR:H, AC:H, AV:L); only confidentiality is impacted through accelerated offline hash cracking.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
3DescriptionCVE.org
Flowise before 3.0.13 uses bcrypt with default salt rounds of 5, providing only 32 iterations instead of the OWASP-recommended minimum of 10 rounds. Attackers can crack password hashes approximately 30 times faster with modern GPU hardware, potentially compromising all user accounts in a database breach scenario.
AnalysisAI
Flowise versions up to and including 3.0.12 hash passwords using bcrypt with a default cost factor of 5 rounds - yielding only 32 iterations versus the OWASP-recommended minimum of 1,024 at 10 rounds - making stored password hashes approximately 30 times faster to crack with modern GPU hardware. All deployments where the PASSWORD_SALT_HASH_ROUNDS environment variable has not been manually overridden to 10 or higher are affected, which represents the majority of real-world installs since defaults predominate. In a database breach scenario, an attacker who obtains the hash table can leverage GPU-accelerated tools to recover plaintext passwords at roughly 300,000 attempts per second versus ~10,000 at the recommended work factor; no public exploit identified at time of analysis.
Technical ContextAI
Flowise is an open-source LLM workflow orchestration platform distributed as an npm package. The weakness resides in packages/server/src/enterprise/utils/encryption.util.ts at lines 5-7, where the getHash() function calls bcrypt.genSaltSync() with a fallback value of 5 when PASSWORD_SALT_HASH_ROUNDS is not set: parseInt(process.env.PASSWORD_SALT_HASH_ROUNDS || '5'). The same insecure default is replicated in the password reset path at account.service.ts:568. CWE-916 (Use of Password Hash With Insufficient Computational Effort) precisely describes this class of defect: bcrypt's security model depends on its configurable cost factor to impose a deliberate computational penalty that keeps pace with hardware advances. At cost factor 5, each hash requires 2^5 = 32 internal iterations; at the OWASP-recommended minimum of 10, this rises to 2^10 = 1,024 iterations - a 32× increase in resistance per attempt. The CPE cpe:2.3:a:flowise:flowise:*:*:*:*:*:*:*:* covers all Flowise releases up through 3.0.12.
RemediationAI
Upgrade Flowise to version 3.0.13 or later, which corrects the default bcrypt salt rounds; the upstream fix is tracked in GitHub PR #5665 at https://github.com/FlowiseAI/Flowise/pull/5665. Prior to upgrading, operators can immediately set the PASSWORD_SALT_HASH_ROUNDS environment variable to a minimum of 10 (OWASP minimum) or preferably 12 (the advisory's recommended balance of security and performance); note that this only affects new hashes - all existing password entries remain stored at 5 rounds and will continue to be crackable at the accelerated rate until users change their passwords. Therefore, after deploying 3.0.13, administrators should trigger a forced password reset for all user accounts to replace legacy low-iteration hashes. Increasing the round count does add measurable latency to login and password reset operations, scaling linearly with cost factor; 12 rounds is advised as a practical upper bound for interactive workloads without perceptible user impact.
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Flowise versions before 3.0.1 allow unauthenticated access to the Custom MCPs feature, which is designed to execute OS c
FlowiseAI Flowise version 2.2.6 contains an arbitrary file upload vulnerability in the /api/v1/attachments endpoint. Una
Remote code execution in Flowise before 3.1.2 allows any authenticated user (or API caller with chatflow view/update per
Flowise is a drag & drop user interface to build a customized large language model flow. Rated critical severity (CVSS 9
Unrestricted file upload in Flowise LLM workflow builder before 3.0.13 via /api/v1/attachments endpoint allows unauthent
Missing authentication on NVD data endpoint in Flowise before 3.0.13 allows unauthenticated access to internal vulnerabi
Remote code execution in Flowise before 3.1.3 arises because its Pyodide Python-code validator (validatePythonCodeForDat
Remote command execution in Flowise <= 3.1.2 lets an authenticated user break out of the vm2/@flowiseai/nodevm JavaScrip
Arbitrary file read and write in FlowiseAI Flowise (versions 2.2.8 through 3.0.5) lets remote unauthenticated attackers
Authenticated remote code execution in FlowiseAI Flowise prior to 3.1.2 allows any user with a valid session or API key
Remote code execution in Flowise before 3.1.3 lets authenticated users abuse the Custom MCP node - when CUSTOM_MCP_PROTO
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today