EUVD-2026-78794
GHSA-4qm7-66jj-3q9w
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Sep 15, 2026
Flowise releases prior to 3.1.4 ship GitHub Actions workflows that interpolate workflow_dispatch inputs such as tag_version and node_version directly into shell run blocks, allowing OS command injection during Docker image builds. The flaw is reachable only by a user who already holds write access to the repository (CVSS 4.0 PR:H), but the payoff is large: arbitrary command execution on the build runner with access to AWS credentials and Docker Hub tokens. No public exploit code or CISA KEV entry was reported at time of analysis, and the vendor has published a fix in 3.1.4 via GitHub Security Advisory GHSA-jrcq-qjw5-xx5q; note that this is a supply-chain/CI risk to the project's own build pipeline and to forks that reuse these workflows, not a runtime flaw in deployed Flowise instances.
Earlier versions of this analysis (1)
Shell command injection in the Docker image build workflows shipped with Flowise before 3.1.4 allows anyone holding repository write access to run arbitrary commands on the project's CI runners by passing crafted workflow_dispatch values such as tag_version and node_version. Because those jobs hold AWS credentials and Docker Hub tokens, successful injection yields direct theft of cloud and registry secrets rather than mere build disruption. The flaw is a code/config issue in the repository's GitHub Actions workflow definitions, not a runtime defect in the Flowise server itself, and is fixed in the 3.1.4 release. There is no CISA KEV listing and no public exploit identified at time of analysis.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Know when Flowise gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Primary rating from Vendor (VulnCheck) · only source for this CVE.
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
4DescriptionCVE.org
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.
Technical POC Analysis
Evidence note: the supplied advisory lists no CVE ID ("No known CVE"); the identifier CVE-2026-91936 in this brief is not present in the evidence.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Threat Intelligence Overview
NVD
CVE.org
EPSS
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Flowise versions before 3.0.1 allow unauthenticated access to the Custom MCPs feature, which is designed to execute OS c
FlowiseAI Flowise version 2.2.6 contains an arbitrary file upload vulnerability in the /api/v1/attachments endpoint. Una
Arbitrary file read and write in Flowise versions prior to 3.0.8 allows an authenticated attacker with access to the flo
Remote code execution in Flowise before 3.1.2 allows any authenticated user (or API caller with chatflow view/update per
Flowise is a drag & drop user interface to build a customized large language model flow. Rated critical severity (CVSS 9
Authenticated users can upload arbitrary files to Flowise 3.0.7 due to missing validation, enabling persistent storage o
Unrestricted file upload in Flowise LLM workflow builder before 3.0.13 via /api/v1/attachments endpoint allows unauthent
Missing authentication on NVD data endpoint in Flowise before 3.0.13 allows unauthenticated access to internal vulnerabi
Authenticated remote code execution in FlowiseAI Flowise (v3.0.1 up to but not including 3.0.8, and later versions when
Remote code execution in Flowise before 3.1.3 arises because its Pyodide Python-code validator (validatePythonCodeForDat
Remote code execution in FlowiseAI Flowise before 3.1.3 lets an attacker execute arbitrary OS commands as the Flowise pr
Exploit-DB