CVE-2026-56269

CVE-2026-56269 is a medium-severity vulnerability in Flowiseai Flowise with a CVSS 3.x base score of 4.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-798.

Key facts

Description

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.

Frequently asked questions

What is CVE-2026-56269?
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.
How severe is CVE-2026-56269?
CVE-2026-56269 has a CVSS 3.x base score of 4.6, rated medium severity. It is exploitable over local access with high attack complexity, requires high privileges and user interaction. Impact on confidentiality is high, integrity low, and availability none.
Is CVE-2026-56269 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-56269?
CVE-2026-56269 affects Flowiseai Flowise. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-56269?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-56269 have an EU (EUVD) identifier?
Yes. CVE-2026-56269 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-38746.
When was CVE-2026-56269 published?
CVE-2026-56269 was published on 2026-06-24 and last updated on 2026-06-26.

References

Affected products (1)

More vulnerabilities in Flowiseai Flowise

All CVEs affecting Flowiseai Flowise →

Other CWE-798 (Use of Hard-coded Credentials) vulnerabilities

Browse all CWE-798 (Use of Hard-coded Credentials) vulnerabilities →