CVE-2026-56269 json
Flowise - Weak Default Token Hash Secret in JWT Token Encryption
published 6mo ago modified 17d ago also GHSA-m7mq-85xj-9x33 , EUVD-2026-38746
- cvss
- 4.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
Flowise before 3.1.0 (npm package flowise, versions 3.0.13 and earlier) uses a weak hardcoded default value 'Secre$t' for the TOKEN_HASH_SECRET environment variable in packages/server/src/enterprise/utils/tempTokenUtils.ts when the variable is not configured. This secret derives the AES-256-CBC key used to encrypt user IDs and workspace IDs in the 'meta' field of JWT tokens. An attacker who knows the default secret can decrypt this metadata to extract internal user and workspace identifiers, and re-encrypt manipulated values such as altered user or workspace IDs. Because the JWT signature is validated separately, decrypting or tampering with this metadata does not by itself grant access, but the disclosure of internal identifiers and possible metadata manipulation could aid privilege escalation or unauthorized data access.
Patch / fix
- npm flowise 3.1.0
- Flowise Flowise 3.1.0
Is CVE-2026-56269 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 4.3 | CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:A/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 4.6 | CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:N |
| CNA | 4.0 | 4.3 | CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:A/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| GitHub | 3.0 | 5.6 | CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | flowise | <3.1.0 |
3.1.0 |
Affected products
- Flowise Flowise
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
github.com
/FlowiseAI/Flowise/security/advisories/GHSA-m7mq-85xj-9x33
vendor-advisory, web, mitigation
-
vulncheck.com
/advisories/flowise-weak-default-token-hash-secret-in-jwt-token-encryption
third-party-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-56269
advisory
-
github.com
/FlowiseAI/Flowise
package
Sources
- CVE List CVE-2026-56269
- GitHub Advisory GHSA-m7mq-85xj-9x33
- NVD CVE-2026-56269
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.