CVE-2026-91936
Flowise before 3.1.4 Script Injection via Docker Workflows
No known exploitation. EPSS puts it in the 37th percentile. No fix published yet.
What to do
No fixed build or workaround is published yet. Limit exposure and watch for a patch.
Steps
Written by AI from the record- Check whether you use Flowise and whether its version is earlier than 3.1.4.
- Upgrade Flowise to version 3.1.4 or later.
- Review who can edit the Flowise project and remove unnecessary write access.
- If untrusted people had write access, replace cloud and container-service access keys used by builds.
What it is
From the CVE record
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.
In plain language
Written by AI from the recordFlowise versions before 3.1.4 have a flaw that lets someone already allowed to change its project files run unwanted commands, so most small businesses should schedule an update rather than treat this as an emergency.
CWE-78 command injection in Flowise Docker build workflows allows repository write-access users to inject shell commands through workflow-dispatch inputs interpolated into run blocks.
If you're affected
- Build-system takeover
- Cloud credential theft
- Docker account token theft
- Unauthorized image changes
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.5% chance of exploitation activity in the next 30 days, which ranks it in the 37th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
7 events over 2 days, from the signal feeds we watch.
- Record updated
- OpenVAS check addedrecord updated
- Publishedweakness classified, att&ck mapped, record updated
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:N
Scored 6.8 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required HighRequires admin or elevated privileges
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)
Impact if exploited
- Confidentiality NoneNo confidentiality impact
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability NoneNo availability impact
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Flowise, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI