Flowise: Weak Default Express Session Secret

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.6 · CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N

EPSS

• CVE-2026-56278: 0.53% estimated exploitation activity in the next 30 days; percentile 44.73 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Detection Method: Kolega.dev Deep Code Scan | Attribute | Value | |---|---| | Location | packages/server/src/enterprise/middleware/passport/index.ts:55 | | Practical Exploitability | High | | Developer Approver | faizan@kolega.ai | 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. 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 EXPRESSSESSIONSECRET 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 EXPRESSSESSIONSECRET is not set (line 55). This secret is used to sign session cookies…

Published by the source

16 Apr 2026, 21:22 UTC

Last modified by the source

8 Jul 2026, 08:27 UTC

Source last checked

26 Oct 2026, 12:48 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-2qqc-p94c-hxwh

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-2qqc-p94c-hxwh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-56278

Advisory: Flowise: Weak Default Express Session Secret
IDs: CVE-2026-56278, GHSA-2qqc-p94c-hxwh
Record: https://patchnext.com/advisories/cve-2026-56278 (revision 2, source checked 26 Oct 2026, 12:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: flowise 3.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm flowise: affected <= 3.0.13; fixed in 3.1.0

## Suggested inspection (read-only)
- `npm ls flowise --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on flowise.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2qqc-p94c-hxwh (OSV record GHSA-2qqc-p94c-hxwh lists affected ranges: npm flowise >=0 <3.1.0 (fixed))
- Verified: https://github.com/advisories/GHSA-2qqc-p94c-hxwh (GitHub-reviewed advisory GHSA-2qqc-p94c-hxwh lists affected ranges: npm flowise >=0 <=3.0.13)

Commands are suggestions: review each one before running it.