CVE-2026-41268: Flowise: Parameter Override Bypass Remote Command Execution

CVE-2026-41268 · Severity: critical · CVSS 9.8 · Published 2026-04-23

Flowise is an AI workflow orchestration platform that allows users to build and deploy chatflows. A critical unauthenticated remote code execution vulnerability enables attackers to execute arbitrary system commands on Flowise instances by bypassing validation checks and injecting malicious environment variables. This impacts any production deployment with API Override enabled and public chatflows containing MCP tool nodes.

Technologies: FlowiseAI Flowise, flowise (npm), flowise-components (npm). Vendors: FlowiseAI, npm.

Quick answers

Is CVE-2026-41268 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-41268 being exploited in the wild.
How severe is CVE-2026-41268?
Critical severity, with a CVSS score of 9.8, published 23 April 2026.
Which products and versions are affected?
flowise (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0; flowise-components (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0.
Is there a fix for CVE-2026-41268?
Yes. flowise (npm): upgrade to 3.1.0 or later; flowise-components (npm): upgrade to 3.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41268 attacked?
It is attacked over the network.
Am I affected by CVE-2026-41268?
Check whether you run FlowiseAI Flowise, flowise (npm) or flowise-components (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • flowise (npm): upgrade to 3.1.0 or later
    npm install flowise@3.1.0
  • flowise-components (npm): upgrade to 3.1.0 or later
    npm install flowise-components@3.1.0

Technical details

The vulnerability stems from two chained flaws in Flowise. First, the FILE-STORAGE:: validation in the replaceInputsWithConfig function (packages/server/src/utils/index.ts) uses .includes() instead of .startsWith(), allowing attackers to embed the keyword anywhere in a parameter string to bypass authorization checks for any parameter, including mcpServerConfig. Second, the Custom MCP node's environment variable blocklist does not include NODE_OPTIONS, permitting attackers to inject this variable with --experimental-loader flags to execute arbitrary JavaScript code before process startup. Exploitation requires API Override to be enabled and the chatflow to be publicly accessible, but needs no authentication or prior knowledge of the target. The attack succeeds through a single HTTP request and was patched in version 3.1.0 (affecting versions ≤3.0.13).

Affected products

  • Flowise Flowise <=3.0.13
  • Flowise flowise-components <=3.0.13

Identifiers

  • CVE-2026-41268
  • GHSA-cvrr-qhgw-2mm6

Timeline

  • 2026-04-16: disclosed
  • 2026-04-16: patched: Version 3.1.0 patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.