Flowise 3.1.3 Remote Code Execution via “node_options” Environment Variable Bypass
What Happened – A newly disclosed CVE‑2026‑58057 affects Flowise < 3.1.3 on Windows. The product’s custom MCP node validates environment variables with a case‑sensitive check, allowing an attacker with authenticated access to inject a node_options variable that bypasses the deny‑list and executes arbitrary code. The issue is patched in version 3.1.3, which switches to an allow‑list model.
Why It Matters for Compliance & Audit Readiness
- The flaw illustrates a classic control‑gap: insufficient validation of configuration inputs that can be leveraged for code execution. SOC 2’s CC6.1 (Change Management) and CC7.1 (System Operations) require documented, enforceable validation rules and evidence that they are applied consistently.
- Continuous‑compliance platforms that map controls to real‑time configuration data can surface this gap before an exploit, providing audit‑ready evidence of remediation.
- The “authenticated‑only” nature of the exploit underscores the need for strong access‑control policies (CC6.2) and regular privileged‑account reviews.
Who Is Affected – SaaS / low‑code workflow platforms, AI‑assisted automation tools, and any organization that runs Flowise on Windows (primarily TECH_SAAS customers).
Recommended Actions
- Verify your Flowise version; upgrade immediately to 3.1.3 or later.
- Review and harden environment‑variable handling: enforce an allow‑list, log all changes, and integrate the validation into your change‑management workflow.
- Map the remediation to SOC 2 controls (CC6.1, CC7.1) and capture configuration snapshots as audit evidence.
- Conduct a privileged‑access review to ensure only authorized users can modify Custom MCP nodes.
Technical Notes – The exploit requires authenticated access to the Custom MCP node, manipulates the node_options variable, and triggers Node.js --require execution. CVSS 2.3 (Medium). Fixed in Flowise 3.1.3 (allow‑list validation). Source: Exploit‑DB 52623