# CVE-2026-56269: flowise — Fixed in 3.1.0

📦 npm

Not in CISA KEV

# CVE-2026-56269 — flowise

CVE-2026-56269 is a Hard-coded Credentials vulnerability in flowise. A fix is available for flowise — see the affected versions and patch details below.

Flowise - Weak Default Token Hash Secret in JWT Token Encryption

Also known as[GHSA-m7mq-85xj-9x33](/vulnerability/GHSA-m7mq-85xj-9x33)

Published

Jun 24, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### No confirmed exploitation observed yet

-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-56269.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs3th percentile — riskier than 3% of all scored CVEsHighest risk

0.00%0.21%0.42%0.63%0.1%0.1%Jul 26Oct 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

`flowise`npm

12Kdownloads / week

## Description

**Detection Method:** Kolega.dev Deep Code Scan

Attribute

Value

Location

packages/server/src/enterprise/utils/tempTokenUtils.ts:31-34

Practical Exploitability

Medium

Developer Approver

[faizan@kolega.ai](mailto:faizan@kolega.ai)

#### Description

The encryption key for token encryption has a weak default value 'Secre$t' when TOKEN\_HASH\_SECRET environment variable is not set.

#### Affected Code

```
const key = crypto
    .createHash('sha256')
    .update(process.env.TOKEN_HASH_SECRET || 'Secre$t')
    .digest()
```

#### Evidence

The default value 'Secre$t' is hardcoded in the source code and is cryptographically weak. This key is used to encrypt user IDs and workspace IDs in JWT tokens.

#### Impact

Token forgery - attackers can decrypt and manipulate encrypted token metadata, potentially changing user IDs or workspace IDs to escalate privileges or access unauthorized data.

#### Recommendation

Require TOKEN\_HASH\_SECRET to be set as a strong random value in environment variables. Throw an error on startup if not configured. Use a minimum of 32 bytes of entropy.

#### Notes

The TOKEN\_HASH\_SECRET has a weak hardcoded default 'Secre$t' (lines 31-34 and 50-53). This secret is used to derive an AES-256-CBC encryption key for encrypting sensitive metadata (user ID and workspace ID) embedded in JWT tokens via encryptToken() called at line 394 of passport/index.ts. If TOKEN\_HASH\_SECRET is not configured, an attacker knowing the default can decrypt the 'meta' field in JWTs to extract user IDs and workspace IDs. While this alone doesn't grant access (the JWT signature is separate), it leaks internal identifiers that could aid other attacks. The .env.example shows '# TOKEN\_HASH\_SECRET='popcorn'' - another weak value, and it's commented out suggesting it's optional. The application should require this secret to be explicitly set with a strong random value.

## Affected Packages

1 total 1 fixed

Ecosystem

Package

Vulnerable range

Fix

📦npm

`flowise` 

all versions

3.1.0`npm install flowise@3.1.0`

## Affected Products

1 product · 1 configurations

Application

`flowise`flowiseai

< 3.1.0

range

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update flowise to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-56269 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
    

## Frequently Asked Questions

\*\*Detection Method:\*\* Kolega.dev Deep Code Scan | Attribute | Value | |---|---| | Location | packages/server/src/enterprise/utils/tempTokenUtils.ts:31-34 | | Practical Exploitability | Medium | | Developer Approver | faizan@kolega.ai | ### Description The encryption key for token encryption has a weak default value 'Secre$t' when TOKEN\_HASH\_SECRET environment variable is not set. ### Affected Code \`\`\` const key = crypto .createHash('sha256') .update(process.env.TOKEN\_HASH\_SECRET || 'Secre$t') .digest() \`\`\` ### Evidence The default value 'Secre$t' is hardcoded in the source code

O3 Security · Impact-Aware SCA

### Is CVE-2026-56269 in your dependencies?

Find it across npm, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)