Is there a patch available for CVE-2026-56269?

Yes, a patch is available for CVE-2026-56269. Update the affected software to the latest version immediately.

Flowise CVE-2026-56269

Q: What is the CVSS score of CVE-2026-56269?

CVE-2026-56269 has a CVSS 4.0 base score of 4.3 (Medium). CVSS vector: 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. EPSS exploitation probability: 0.1%.

EUVD-2026-38746 MEDIUM

Use of Hard-coded Credentials (CWE-798)

2026-06-24 VulnCheck

Authentication Bypass Privilege Escalation Node.js Flowise

4.3

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

4.3 MEDIUM

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

vuln.today AI

7.1 HIGH

Authenticated network users can decrypt JWT metadata using the publicly known default key; JWT signature validation independently limits integrity impact to low.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Local

Attack Complexity

High

Privileges Required

High

User Interaction

Scope

Lifecycle Timeline

Patch available

Jun 24, 2026 - 13:01 EUVD

Source Code Evidence Fetched

Jun 24, 2026 - 12:23 vuln.today

Analysis Generated

Jun 24, 2026 - 12:23 vuln.today

DescriptionCVE.org

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.

AnalysisAI

Flowise versions 3.0.13 and earlier silently fall back to a hardcoded AES-256-CBC encryption key derived from the publicly known literal 'Secre$t' when TOKEN_HASH_SECRET is not configured, exposing the user and workspace IDs encoded in the 'meta' field of every JWT token issued by an unconfigured deployment. An authenticated user or network-positioned attacker who obtains any valid JWT can decrypt this metadata using the default key - now disclosed in the GHSA advisory and source code - and re-encrypt manipulated identifiers to probe downstream access controls. JWT signature validation is handled independently, so this does not constitute standalone token forgery, but identifier disclosure and metadata manipulation create a realistic stepping stone toward privilege escalation or unauthorized workspace access in multi-tenant deployments. No active exploitation is confirmed (not in CISA KEV) and no public exploit code has been identified at time of analysis; vendor-released patch Flowise 3.1.0 is available.

Technical ContextAI

Flowise is an open-source Node.js LLM orchestration platform distributed as the npm package 'flowise'. The vulnerable code at packages/server/src/enterprise/utils/tempTokenUtils.ts:31-34 computes the AES-256-CBC encryption key by SHA-256 hashing the TOKEN_HASH_SECRET environment variable, with a fallback to the string literal 'Secre$t' when the variable is absent: crypto.createHash('sha256').update(process.env.TOKEN_HASH_SECRET || 'Secre$t').digest(). This derived key is used by encryptToken() (called at passport/index.ts:394) to encrypt the 'meta' field of JWTs, which carries enterprise-tier context including user IDs and workspace IDs. The root cause is CWE-798 (Use of Hard-coded Credentials): the .env.example ships with the variable commented out ('

TOKEN_HASH_SECRET='popcorn''), making an unconfigured state the operational default for new deployments. AES-256-CBC encryption with a predictable key provides no meaningful confidentiality once the key value is publicly known. Affected CPE: cpe:2.3:a:flowise:flowise::::::::.

RemediationAI

Upgrade the flowise npm package to version 3.1.0 or later, which is the vendor-confirmed fix per the GHSA advisory at https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-m7mq-85xj-9x33. As an immediate compensating control that applies to all affected versions prior to upgrading, explicitly set TOKEN_HASH_SECRET to a cryptographically strong random string of at least 32 bytes of entropy in the deployment environment - this eliminates use of the hardcoded default regardless of installed version, but note that changing the secret will invalidate the 'meta' field of all previously issued JWTs, requiring affected users to re-authenticate. Operators should audit .env files and container environment configurations, as the .env.example ships with this variable commented out, making the misconfigured state the default for new installs. Organizations should additionally consider treating all internal user and workspace IDs previously transmitted via unconfigured Flowise instances as potentially disclosed and assess whether downstream access controls depend on those identifiers remaining opaque. The recommendation from Kolega.dev is to enforce startup failure when TOKEN_HASH_SECRET is absent, ensuring the weak default cannot be silently activated in future deployments.