| Component | Flowise |
| Severity | medium (CVSS 4.6) |
| CVSS vector | CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:N |
| Published (NVD) | 2026-06-24 |
| Last modified | 2026-06-26 |
| Affected versions | flowise < 3.1.0 |
| Fixed in | 3.1.0 |
| Weakness | CWE-798 |
| CISA KEV | not 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.
What to do
- Upgrade Flowise to
3.1.0or later. - Do not expose the component's API or UI to the internet without authentication in front of it.
Sources
- NVD: CVE-2026-56269
- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-m7mq-85xj-9x33
- https://www.vulncheck.com/advisories/flowise-weak-default-token-hash-secret-in-jwt-token-encryption
Other Flowise CVEs
Flowise through 3.1.4 exposes GET /api/v1/upsert-history/:id and PATCH /api/v1/upsert-history without route-level permission checks, and the...
Flowise through 3.1.4 does not enforce authorization on the BullMQ admin dashboard. When the server runs in queue mode with the dashboard en...
Flowise through 3.1.4 contains missing route-level RBAC checks on chat message endpoints that allow low-privileged API keys to read and dele...
Flowise (npm packages `flowise` and `flowise-components`) through 3.1.4 looks up credentials by ID without filtering on the requesting user'...
Flowise through 3.1.4 resolves SSO and local-password users solely by email without storing provider or subject identifier bindings, allowin...
Flowise through 3.1.4 (Enterprise/platform mode with SSO enabled) contains an authentication bypass in the SSO login path. When an SSO callb...