Medium severity · published Jun 24, 2026
CVE-2026-56269
Flowise - Weak Default Token Hash Secret in JWT Token Encryption
4.6
CVSS
0.1%
EPSS
No
On KEV
Description
Flowise before 3.1.0 (npm package flowise, versions 3.0.13 and earlier) uses a weak hardcoded default value 'Secre$t' for the TOKEN_HASH_SECRET environment variable in packages/server/src/enterprise/utils/tempTokenUtils.ts when the variable is not configured. This secret derives the AES-256-CBC key used to encrypt user IDs and workspace IDs in the 'meta' field of JWT tokens. An attacker who knows the default secret can decrypt this metadata to extract internal user and workspace identifiers, and re-encrypt manipulated values such as altered user or workspace IDs. Because the JWT signature is validated separately, decrypting or tampering with this metadata does not by itself grant access, but the disclosure of internal identifiers and possible metadata manipulation could aid privilege escalation or unauthorized data access.
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:N
Attack vector
Local
Complexity
High
Privileges
High
User interaction
Required
Confidentiality
High
Integrity
Low
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.1% · higher than 3% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
FL
Flowise · Flowise
before 3.1.0 · source: vendor, NVD
Affected product
FL
Flowise
Flowise
More from Flowise
9.9
CVE-2026-56274
Flowise - Remote Code Execution via MCP Security Bypass in validateCommandFlags and validateArgsForLocalFileAccess
9.8
CVE-2026-56271
Flowise - Weak Default JWT Secrets in Authentication Middleware
9.8
CVE-2025-71338
Flowise through 2.2.7 - Arbitrary File Write to Remote Code Execution via document-store API
9.8
CVE-2025-71336
Flowise - Unsandboxed Remote Code Execution via Custom MCP
9.8
CVE-2025-71334
Flowise - Arbitrary File Access via Missing Chat Flow ID Validation