Medium Authentication

CVE-2026-56269 — Flowise - Weak Default Token Hash Secret in JWT Token Encryption

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.

Published Jun 24, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulnCheck

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.1% (30-day exploitation probability)+0
Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.13%

ahead of 2% of scored CVEs · Oct 14, 2026

Affects

Flowise

CVSS base

4.6

Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented mitigation — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Flowise Flowise, Flowiseai Flowise).
Apply the documented mitigations until a definitive fix is available.
Exploitation requires user interaction: tighten email/web filtering and warn affected users.
Search available logs for exploit probes matching the vulnerability class (authentication), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Flowise	Flowise	< 3.1.0	Vulnerable	CVE Program (cve.org) e CISA ADP
Flowiseai	Flowise	< 3.1.0	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

High

Privileges required

High

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
4.3	CVSS 4.0	Medium	—	—	disclosure@vulncheck.com via NIST National Vulnerability Database
4.3	CVSS 4.0	Medium	—	—	VulnCheck via CVE Program (cve.org) e CISA ADP
4.6	CVSS 3.1	Medium	0.3	4.2	disclosure@vulncheck.com via NIST National Vulnerability Database
4.6	CVSS 3.1	Medium	—	—	VulnCheck via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:N (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-798 · Use of Hard-coded Credentials

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.13%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Review authentication logs: logins without MFA, anomalous sessions and recently created accounts.

endpoint telemetry (EDR)authentication logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · flowise/flowise
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
Fix documented
Oct 13, 2026 · NIST National Vulnerability Database
CVSS changed · 4.6
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Jun 24, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

2 on the record

github.com/FlowiseAI/Flowise/security/advisories/GHSA-m7mq-85xj-9x33
Mitigation, Vendor Advisory, vendor-advisory, NIST National Vulnerability Database
www.vulncheck.com/advisories/flowise-weak-default-token-hash-secret-in-jwt-token-encryp
Third Party Advisory, third-party-advisory, NIST National Vulnerability Database

Elsewhere on this site

Flowise
every CVE for this vendor

Authentication
same class

CWE-798
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2026-91936 Flowise before 3.1.4 Script Injection via Docker Workflows Sep 15, 2026
High CVE-2026-91937 Flowise before 3.1.4 NoSQL Injection via sessionId Sep 15, 2026
High CVE-2026-91938 Flowise before 3.1.4 Server-Side Request Forgery via document loaders Sep 15, 2026
High CVE-2026-91933 Flowise before 3.1.4 Authorization Bypass via openai-realtime Sep 15, 2026
High CVE-2026-91932 Flowise before 3.1.4 Remote Code Execution via cwd Parameter Sep 15, 2026
High CVE-2026-91934 Flowise before 3.1.4 Remote Code Execution via SQL Database Chain Sep 15, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-56269 is "Flowise - Weak Default Token Hash Secret in JWT Token Encryption", rated Medium. It affects Flowise (Flowise); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.6 describes technical severity. EPSS 0.13% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.