Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.3
Flowise: Weak Default JWT Secrets Expose User Authentication
GHSA-cc4f-hjpj-g9p8
Summary
Flowise has weak default settings for JSON Web Tokens (JWTs) that can be exploited by attackers to impersonate any user, bypassing authentication and potentially gaining admin access. This is a critical issue that requires immediate attention. To fix it, Flowise developers should remove the default secrets, ensure they are randomly generated, and implement a secret rotation mechanism to prevent unauthorized access.
What to do
- Update henryheng flowise to version 3.1.0.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| npm | henryheng | flowise |
< 3.1.0 Fix: upgrade to 3.1.0
|
| – | flowise | flowise | < 3.1.0 |
Original title
Flowise - Weak Default JWT Secrets in Authentication Middleware
Original description
Flowise before 3.1.0 (affected versions 3.0.13 and earlier) uses weak hardcoded default JWT secrets ('auth_token', 'refresh_token') and default audience and issuer values ('AUDIENCE', 'ISSUER') in the enterprise passport authentication middleware (packages/server/src/enterprise/middleware/passport/index.ts). When the corresponding environment variables (JWT_AUTH_TOKEN_SECRET, JWT_REFRESH_TOKEN_SECRET, JWT_AUDIENCE, JWT_ISSUER) are not set, the application silently falls back to these publicly known defaults, allowing an attacker to forge valid JWTs and impersonate any user, including administrators, resulting in authentication bypass.
osv CVSS3.1
5.6
Vulnerability type
CWE-327
Use of a Broken Cryptographic Algorithm
CWE-321
Use of Hard-coded Cryptographic Key
Published: 12 Jul 2026 · Updated: 13 Jul 2026 · First seen: 16 Apr 2026