# CVE-2026-91936: Flowise before 3.1.4 Script Injection via Docker Workflows

> Attackers with repository write access can inject shell commands into Docker workflows to execute arbitrary code and steal credentials.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-4qm7-66jj-3q9w, GHSA-jrcq-qjw5-xx5q

## What is CVE-2026-91936?

CVE-2026-91936 is a high-severity command injection vulnerability in FlowiseAI Flowise, published on 15 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Flowise versions before 3.1.4 contain a script injection vulnerability in Docker image build workflows where workflow_dispatch inputs are directly interpolated into shell run blocks. Attackers with repository write access can inject shell metacharacters through inputs like tag_version and node_version to execute arbitrary commands and steal AWS credentials and Docker Hub tokens.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-91936 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91936 is a high-severity command injection vulnerability in FlowiseAI Flowise, published on 15 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91936 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-91936/ (Markdown: https://insights.sbomify.com/CVE-2026-91936/index.md)
```

## Sources

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

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