Vulnerability · Published Jun 24, 2026 · Assigned by VulnCheck
CVE-2026-56269Flowise - Weak Default Token Hash Secret in JWT Token Encryption
Medium 4.6
In plain English
A medium-severity hard-coded credentials in Flowise from Flowise. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 3% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| npm | flowise | 3.1.0 | GHSA-m7mq-85xj-9x33 |
Affected products (as reported)
Weakness: CWE-798 · Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:N
References
- GitHub Security Advisory (GHSA-m7mq-85xj-9x33) vendor-advisory
- VulnCheck Advisory: Flowise - Weak Default Token Hash Secret in JWT Token Encryption third-party-advisory