GHSA-2qqc-p94c-hxwh: Flowise: Weak Default Express Session Secret
Detection Method: Kolega.dev Deep Code Scan Attribute Value ------ Location packages/server/src/enterprise/middleware/passport/index.ts:55 Practical Exploitability High Developer Approver [email protected] Description Express session secret has a weak default value 'flowise' when EXPRESSSESSIONSECRET is not set. Affected Code Evidence The default session secret 'flowise' is publicly visible and weak.
Published Apr 16, 2026
Affected packages
flowise
- Ecosystem
- npm
- Affected
- <= 3.0.13
- Fixed in
- 3.1.0
- Check
npm ls flowise
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Detection Method: Kolega.dev Deep Code Scan
| Attribute | Value | | Location | packages/server/src/enterprise/middleware/passport/index.ts:55 | | Practical Exploitability | High | | Developer Approver | [email protected] |
Description
Express session secret has a weak default value 'flowise' when EXPRESS_SESSION_SECRET is not set.
Affected Code
secret: process.env.EXPRESS_SESSION_SECRET || 'flowise'Evidence
The default session secret 'flowise' is publicly visible and weak. Session cookies signed with this secret can be forged by attackers.
Impact
Session hijacking and forgery - attackers can create arbitrary session cookies to impersonate any user, bypassing all authentication mechanisms.
Recommendation
Require EXPRESS_SESSION_SECRET to be set with a strong random value. Throw an error on startup if not configured. Use cryptographically strong random strings (minimum 256 bits).
Notes
The Express session secret defaults to the string 'flowise' when EXPRESS_SESSION_SECRET is not set (line 55). This secret is used to sign session cookies via express-session middleware. Since 'flowise' is publicly visible in the source code, an attacker can forge valid session cookies to impersonate any user without authentication. The .env.example file has this commented out (# EXPRESS_SESSION_SECRET=flowise), implying it's optional, which compounds the risk. Unlike development-only defaults, this code path is active in production if the environment variable is not set. The application should require EXPRESS_SESSION_SECRET to be explicitly configured with a cryptographically strong random value and fail to start otherwise.
Credited to kolega-ai-dev.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Flowise vulnerabilities
All Flowise entriesCVE-2026-73483
Flowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromium
critical9.4Oct 7, 2026CVE-2026-73487
Flowise Prompt Injection to RCE and SSRF via CSV/Airtable Agent Python Validator Bypass
critical9.0Oct 7, 2026CVE-2026-69250
Flowise: Unauthenticated OAuth2 Refresh Enables Non-Blind SSRF and Secret Exfiltration
high8.5Aug 4, 2026CVE-2026-69251
Flowise RCE via TypeORM DataSource
critical9.0Aug 4, 2026CVE-2026-69252
Flowise: Missing authorization on `/api/v1/files` allows low-privileged API keys to list and delete files across workspaces within the same organization
high7.2Aug 4, 2026CVE-2026-69253
Flowise Sandbox Escape to RCE
critical9.0Aug 4, 2026
