Executive brief
Flowise uses a weak hard-coded default secret ('Secre$t') for token encryption when the TOKEN_HASH_SECRET environment variable is not set, potentially allowing token metadata manipulation.
Affected products
- npm flowise
Junglewise Threat Intelligence
Flowise hard-coded default secret in token encryption
Severity: medium · CVSS 5.6 · Published 2026-04-16
Technologies: flowise (npm). Vendors: npm.
Related threats
- Flowise before 3.1.3 contains an incomplete credential redaction vulnerability in the GET /api/v1/credentials/:id endpoint that returns decr
- Flowise before 3.1.4 fails to validate chatflow visibility in the unauthenticated text-to-speech endpoint, allowing attackers to abuse priva
- Flowise versions before 3.1.3 contain an insecure direct object reference vulnerability in the GET /api/v1/organization/customer-default-sou
- Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, the POST /api/v1/oauth2-credential/
- Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, a prompt injection sent to a chatfl