mediumCVSS 4.6NVD status: Analyzed

CVE-2026-56269

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/tempTokenUti...

ComponentFlowise
Severitymedium (CVSS 4.6)
CVSS vectorCVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:N
Published (NVD)2026-06-24
Last modified2026-06-26
Affected versions
flowise < 3.1.0
Fixed in3.1.0
WeaknessCWE-798
CISA KEVnot listed

NVD 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.

Does CVE-2026-56269 hit the version you run?Paste your docker-compose.yml, requirements.txt or package.json. The scanner checks your pinned versions against this CVE and every other one we track for Flowise.
Check my stack

What to do

  • Upgrade Flowise to 3.1.0 or later.
  • Do not expose the component's API or UI to the internet without authentication in front of it.

Sources

Other Flowise CVEs

All Flowise CVEs