CVE-2026-69251

CRITICALPre-NVD 9.09.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 46% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.0Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.0
EG Score
9.0(medium)
EG Risk
61(Track*)
EG Risk 61/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
54%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 4, 2026

Advisory Details (1)

Auto-updated Aug 4, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Flowise RCE via TypeORM DataSource · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-g32j-mmxr-gfq5

Vendor Advisories for CVE-2026-69251(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFixed inDependents
flowise—3.1.3—
flowise-components—3.1.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 01:31 UTCEG score recompute
  2. 2026-08-20 22:56 UTCEPSS rescore
  3. 2026-08-19 18:56 UTCEG score recompute
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 15:48 UTCEG score recompute
  6. 2026-08-18 13:49 UTCEPSS rescore
  7. 2026-08-18 13:49 UTCEPSS rescore
  8. 2026-08-17 17:07 UTCEG score recompute
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 15:01 UTCEG score recompute
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 06:20 UTCEG score recompute
  14. 2026-08-16 02:15 UTCEPSS rescore
  15. 2026-08-15 04:21 UTCEG score recompute
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 02:19 UTCEG score recompute
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-12 15:33 UTCEG score recompute
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-11 17:53 UTCEG score recompute
  22. 2026-08-11 13:34 UTCEG score recompute
  23. 2026-08-11 00:34 UTCEG score recompute
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-09 17:54 UTCEG score recompute
Show 10 more
  1. 2026-08-09 13:47 UTCEPSS rescore
  2. 2026-08-07 18:14 UTCEG score recompute
  3. 2026-08-06 16:14 UTCEG score recompute
  4. 2026-08-06 13:47 UTCEPSS rescore
  5. 2026-08-05 22:54 UTCEG score recompute
  6. 2026-08-05 19:17 UTCEPSS rescore
  7. 2026-08-05 19:17 UTCEPSS rescore
  8. 2026-08-04 15:19 UTCEG score recompute
  9. 2026-08-04 14:48 UTCEG score recompute
  10. 2026-08-04 14:47 UTCMITRE cvelistV5first tracked

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-69251.yaml
    First seen Jan 1, 2026

    Flowise < 3.1.3 - Remote Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-69251?
CVE-2026-69251 is a critical vulnerability published on August 4, 2026. 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…
When was CVE-2026-69251 disclosed?
CVE-2026-69251 was first published in the National Vulnerability Database on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69251 actively exploited?
CVE-2026-69251 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 46.5% of all scored CVEs.
What is the CVSS score of CVE-2026-69251?
CVE-2026-69251 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2026-69251?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69251, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69251

Explore →

Is Your Infrastructure Affected by CVE-2026-69251?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs