# CVE-2026-91932: Flowise before 3.1.4 Remote Code Execution via cwd Parameter

> Authenticated attackers can achieve remote code execution in Flowise by bypassing path validation via the cwd parameter in MCP server configuration.

- **Severity:** Critical 9.0 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-63x5-9mcr-7447, GHSA-x7x8-95gh-42xm

## What is CVE-2026-91932?

CVE-2026-91932 is a critical command injection vulnerability in FlowiseAI Flowise, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Flowise before 3.1.4 contains a validation bypass vulnerability in MCP server configuration allowing authenticated attackers remote code execution through an unvalidated cwd parameter. Attackers can bypass path validation using clean filenames in the args array while controlling the working directory to execute malicious code.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-91932 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91932 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91932 is a critical command injection vulnerability in FlowiseAI Flowise, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91932 exists.

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-91932/ (Markdown: https://insights.sbomify.com/CVE-2026-91932/index.md)
```

## Sources

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

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