Authenticated command execution via Custom MCP validation bypass
Published Aug 13, 2026 · Updated Aug 13, 2026
Code injection in the Custom MCP node in Flowise before 3.1.3 allows remote authenticated users to execute commands on the server. Its stdio configuration validation permits dangerous Python environment variables and lets Node resolve proc/self/environ from the root working directory. Exploitation requires an authenticated account and CUSTOM_MCP_PROTOCOL set to stdio, and successful execution compromises the application host.
Summary
What happened
Code injection in the Custom MCP node in Flowise before 3.1.3 allows remote authenticated users to execute commands on the server. Its stdio configuration validation permits dangerous Python environment variables and lets Node resolve proc/self/environ from the root working directory. Exploitation requires an authenticated account and CUSTOM_MCP_PROTOCOL set to stdio, and successful execution compromises the application host.
The record
- CVE
- CVE-2026-73601
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- CWE-95, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 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.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
- Custom MCP Node proc environment proof of conceptproof of concept · demonstrated
- Custom MCP Python environment-variable proof of conceptproof of concept · demonstrated
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