# CVE-2026-91934: Flowise before 3.1.4 Remote Code Execution via SQL Database Chain


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-8cvx-xcmg-xfxm, GHSA-pwfj-wh95-7mwp

## What is CVE-2026-91934?

CVE-2026-91934 is a high-severity vulnerability in FlowiseAI Flowise, published on 15 Sep 2026. 

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-91934?


## How do I fix CVE-2026-91934?

No fix has been published for CVE-2026-91934 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-91934 being exploited?

There is no known exploitation of CVE-2026-91934 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-91934 and fix it if it is affected.

What it is: CVE-2026-91934 is a high-severity vulnerability in FlowiseAI Flowise, published on 15 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-91934 in the wild and no public exploit code.

Affected product: FlowiseAI Flowise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-91934/ (Markdown: https://insights.sbomify.com/CVE-2026-91934/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-91934
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-91934
- OSV: https://osv.dev/vulnerability/CVE-2026-91934

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-91934/
Summaries are generated and may contain mistakes; the official description above is the record.