CVE-2026-91934

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-15. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

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

Flowise versions before 3.1.4 fail to validate file paths in the SQL Database Chain node when connecting to SQLite databases, allowing authenticated attackers to write arbitrary files. Attackers can write malicious SQLite databases to system directories or inject files into the web root to execute commands or perform stored XSS attacks.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 16, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
Patch available. Sources: github.
generic

Flowise before 3.1.4 Remote Code Execution via SQL Database Chain | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-before-3.1.4-remote-code-execution-via-sql-database-chain
github Patch Available

Flowise RCE via SQL Database Chain Node · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-pwfj-wh95-7mwp

Vendor Advisories for CVE-2026-91934(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 41× 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-09-25 12:58 UTCGHSA enrichment
  2. 2026-09-25 00:01 UTCEG score recompute
  3. 2026-09-25 00:01 UTCGHSA enrichment
  4. 2026-09-24 14:04 UTCEPSS rescore
  5. 2026-09-24 10:45 UTCGHSA enrichment
  6. 2026-09-23 21:51 UTCEG score recompute
  7. 2026-09-23 21:51 UTCGHSA enrichment
  8. 2026-09-23 17:54 UTCEPSS rescore
  9. 2026-09-23 08:57 UTCGHSA enrichment
  10. 2026-09-22 20:02 UTCEG score recompute
  11. 2026-09-22 20:02 UTCGHSA enrichment
  12. 2026-09-22 16:01 UTCEPSS rescore
  13. 2026-09-22 07:08 UTCEG score recompute
  14. 2026-09-22 07:07 UTCGHSA enrichment
  15. 2026-09-21 21:09 UTCEPSS rescore
  16. 2026-09-21 18:13 UTCGHSA enrichment
  17. 2026-09-21 05:18 UTCEG score recompute
  18. 2026-09-21 05:17 UTCGHSA enrichment
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-20 16:22 UTCGHSA enrichment
  21. 2026-09-20 03:27 UTCEG score recompute
  22. 2026-09-20 03:27 UTCGHSA enrichment
  23. 2026-09-19 14:33 UTCGHSA enrichment
  24. 2026-09-19 01:38 UTCEG score recompute
  25. 2026-09-19 01:38 UTCGHSA enrichment
Show 16 more
  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 12:44 UTCGHSA enrichment
  3. 2026-09-17 23:49 UTCEG score recompute
  4. 2026-09-17 23:49 UTCGHSA enrichment
  5. 2026-09-17 19:32 UTCEPSS rescore
  6. 2026-09-17 10:02 UTCGHSA enrichment
  7. 2026-09-16 21:07 UTCGHSA enrichment
  8. 2026-09-16 18:23 UTCEG score recompute
  9. 2026-09-16 18:22 UTCGHSA enrichment
  10. 2026-09-16 14:09 UTCEPSS rescore
  11. 2026-09-16 05:27 UTCEG score recompute
  12. 2026-09-16 05:27 UTCGHSA enrichment
  13. 2026-09-15 16:33 UTCEG score recompute
  14. 2026-09-15 15:48 UTCEG score recompute
  15. 2026-09-15 15:24 UTCEG score recompute
  16. 2026-09-15 15:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-91934?
CVE-2026-91934 is a high vulnerability published on September 15, 2026. Flowise versions before 3.1.4 fail to validate file paths in the SQL Database Chain node when connecting to SQLite databases, allowing authenticated attackers to write arbitrary files. Attackers can write malicious SQLite databases to system directories or inject files into the web root to execute…
When was CVE-2026-91934 disclosed?
CVE-2026-91934 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-91934 actively exploited?
CVE-2026-91934 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 47.5% of all scored CVEs.
What is the CVSS score of CVE-2026-91934?
CVE-2026-91934 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-91934?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-91934, 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

Explore the affected products and dependency analysis for CVE-2026-91934

Explore →

Is Your Infrastructure Affected by CVE-2026-91934?

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