CVE-2026-69251 json
Flowise RCE via TypeORM DataSource
published 2026-08-04 3 mo ago modified 2026-09-14 55 d ago also GHSA-g32j-mmxr-gfq5 , EUVD-2026-52701
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.7%
- EPSS 2.7% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, Flowise record manager and agent memory nodes allowed users to set arbitrary TypeORM DataSource options through the additionalConfig input in packages/components/nodes/recordmanager/MySQLRecordManager/MySQLrecordManager.ts, packages/components/nodes/recordmanager/PostgresRecordManager/PostgresRecordManager.ts, packages/components/nodes/recordmanager/SQLiteRecordManager/SQLiteRecordManager.ts, packages/components/nodes/memory/AgentMemory/MySQLAgentMemory/MySQLAgentMemory.ts, and packages/components/nodes/memory/AgentMemory/AgentMemory.ts. TypeORM DataSource options such as entities, subscribers, and migrations can load local JavaScript files, allowing an authenticated user to execute arbitrary code on the server by uploading a JavaScript payload and referencing it from additionalConfig.entities. This issue is fixed in version 3.1.3.
Patch / fix
- npm flowise 3.1.3
- npm flowise-components 3.1.3
- flowiseai flowise 3.1.3
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 3 mo ago
Exploit prediction
2.74% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template Flowise < 3.1.3 - Remote Code Execution nuclei detection template
- github.com https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-g32j-mmxr-gfq5 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H |
| CNA | 4.0 | 9.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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 |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | flowise | <3.1.3 |
3.1.3 |
| npm | flowise-components | <3.1.3 |
3.1.3 |
Affected products
- FlowiseAI Flowise
- FlowiseAI flowise-components
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
github.com
/FlowiseAI/Flowise/security/advisories/GHSA-g32j-mmxr-gfq5
exploit, web, vendor-advisory
-
github.com
/FlowiseAI/Flowise
package
Sources
- CVE List CVE-2026-69251
- GitHub Advisory GHSA-g32j-mmxr-gfq5
- NVD CVE-2026-69251
Fencer Vulns 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.