Authenticated code execution via attacker-controlled npx packages
Published Sep 15, 2026 · Updated Sep 15, 2026
Remote code execution in Flowise before 3.1.4 allows remote authenticated users to run code through crafted Custom MCP npx package names. The Custom MCP node passes attacker-controlled package names from mcpServerConfig to npx, causing npm package code to execute on the server. An authenticated account with Custom MCP configuration access is required, and successful exploitation compromises the application under Flowise's service privileges.
Summary
What happened
Remote code execution in Flowise before 3.1.4 allows remote authenticated users to run code through crafted Custom MCP npx package names. The Custom MCP node passes attacker-controlled package names from mcpServerConfig to npx, causing npm package code to execute on the server. An authenticated account with Custom MCP configuration access is required, and successful exploitation compromises the application under Flowise's service privileges.
The record
- CVE
- CVE-2026-91931
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.1.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo