CVE-2026-69263: Flowise Remote Code Execution Vulnerability

HIGH
Advisory Identifier: GHSA-xc48-889x-5qmw
CWE-184
Published
Advisory Summary

CVE-2026-69263 is a HIGH remote code execution vulnerability (CWE-184: Incomplete List of Disallowed Inputs) affecting Flowise libraries in the npm ecosystem. The issue involves cve-2025-8943 patch bypass: npm_config_yes bypasses mcp environment variable blocklist (unauthenticated rce). Remediation is available by upgrading affected packages to version 3.1.3.

CVE-2026-69263 at a Glance

CVE Identifier CVE-2026-69263
GHSA Identifier GHSA-xc48-889x-5qmw
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-184: Incomplete List of Disallowed Inputs
Affected Product Flowise
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-69263

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.1.3
npm install flowise@3.1.3
flowise-components fixed: 3.1.3
npm install flowise-components@3.1.3
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 CVE-2026-69263, 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.1.3), 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-184: Incomplete List of Disallowed Inputs, where the product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete. 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 mitigation shipped for CVE-2025-8943 blocks the `-y` and `--yes` flags on `npx` to stop auto-installation of arbitrary packages. That flag filter works. The environment-variable check in the same patch denies only four variable names by exact string match, and `npm` reads its configuration directly from `npm_config_*` environment variables. Setting `npm_config_yes=true` reproduces the `--yes` behaviour the flag filter is meant to prevent, so `npx` auto-installs and executes the named package. The mitigation is fully bypassed. This works with the MCP security check enabled (`CUSTOM_MCP_SECURITY_CHECK=true`). On a default Flowise deployment, which ships with no authentication, the result is unauthenticated remote code execution. ## Root cause The patch treats this as a flag-filtering problem, but the behaviour gated by `--yes` is also reachable through `npm`'s environment-based configuration. The same is true for the other permitted interpreters, `node` and `python3`. A denylist of variable names cannot enumerate every environment variable that alters execution, so the control is incomplete by construction. The fix is to allowlist (or strip) the environment before it reaches the child process, not to extend the denylist. ## Affected version Flowise 3.1.1, current as of 2026-03-29. ## Details Validation happens in `packages/components/nodes/tools/MCP/core.ts`. Two functions run in sequence before any MCP server launches: `validateCommandFlags` and `validateEnvironmentVariables`. `validateCommandFlags` is thorough. It blocks `-y` and `--yes` along with a comprehensive set of dangerous flags across `npx`, `node`, `python`, `python3`, and `docker`. That part of the patch is sound. The gap is in `validateEnvironmentVariables`: ```typescript export const validateEnvironmentVariables = (env: Record<string, any>): void => { const dangerousEnvVars = ['PATH', 'LD_LIBRARY_PATH', 'DYLD_LIBRARY_PATH', 'NODE_OPTIONS'] for (const [key, value] of Object.entries(env)) { if (dangerousEnvVars.includes(key)) { throw new Error(`Environment variable '${key}' modification is not allowed`) } if (typeof value === 'string' && value.includes('\0')) { throw new Error(`Environment variable '${key}' contains null byte`) } } } ``` The blocklist is a hardcoded four-item array checked by exact match. Any variable not in that list passes through unchecked. `npm_config_yes` is npm's documented mechanism for setting the `yes` config via the environment. Set to `true`, it causes `npx` to auto-install without prompting, which is exactly what the `-y` and `--yes` flag blocks are intended to prevent. ## Proof of concept The following MCP server configuration bypasses the patch with `CUSTOM_MCP_SECURITY_CHECK=true`: ```json { "mcpServers": { "bypass": { "command": "npx", "args": ["malicious-package"], "env": { "npm_config_yes": "true" } } } } ``` Execution path: 1. `validateCommandFlags` passes, because `args` contains no blocked flags. 2. `validateEnvironmentVariables` passes, because `npm_config_yes` is not in the four-item blocklist. 3. `npx` auto-installs and executes the named package with the privileges of the Flowise process. On a default deployment with no authentication, any unauthenticated user who can reach the Flowise API can trigger this. ## Additional bypass vectors (same root cause) The following variables are also absent from the blocklist and influence execution through the other permitted interpreters: | Variable | Command | Effect | |---|---|---| | `npm_config_prefix` | `npx` | Redirects package installation to attacker-controlled path | | `npm_config_userconfig` | `npx` | Loads attacker-controlled `.npmrc` configuration | | `NODE_PATH` | `node` | Loads modules from attacker-controlled path | | `PYTHONPATH` | `python3` | Loads modules from attacker-controlled path | | `PYTHONSTARTUP` | `python3` | Executes a file on interpreter startup (interactive sessions only) | ## Impact Full remote code execution with the privileges of the Flowise process. On default deployments with no authentication, no credentials are required. ## Remediation Strip the `env` object before passing it to the child process, or replace the name blocklist with an allowlist of explicitly permitted variables. Adding the known dangerous variables to the blocklist (`npm_config_yes`, `npm_config_prefix`, `npm_config_userconfig`, `NODE_PATH`, `PYTHONPATH`, `PYTHONSTARTUP`) narrows the immediate gap but is a stopgap. Any future permitted interpreter reintroduces the same class of bypass. ## References - CVE-2025-8943 - CWE-184: Incomplete List of Disallowed Inputs

CVE-2026-69263 Affected Flowise Versions

2 component(s)
Fixed Versions:
3.1.3
Product / Package Ecosystem Affected Versions Fixed Version
flowise
npm
< 3.1.3
3.1.3
flowise-components
npm
< 3.1.3
3.1.3

References

Frequently Asked Questions

What is CVE-2026-69263?
CVE-2026-69263 is a security vulnerability in Flowise involving CVE-2025-8943 Patch Bypass: npm_config_yes bypasses MCP environment variable blocklist (Unauthenticated RCE) under CWE-184: Incomplete List of Disallowed Inputs.
Which Flowise versions are affected?
Affected versions include releases prior to 3.1.3 across affected packages: flowise, flowise-components.
What version fixes CVE-2026-69263?
Upgrading to 3.1.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is flowise affected?
Yes, flowise is affected in releases prior to 3.1.3. Upgrade your dependency to 3.1.3 or later.
Is flowise-components affected?
Yes, flowise-components is affected in releases prior to 3.1.3. Upgrade your dependency to 3.1.3 or later.
What CWE is associated with CVE-2026-69263?
CVE-2026-69263 is classified under CWE-184: Incomplete List of Disallowed Inputs (The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete.).
How can I check npm dependencies for CVE-2026-69263?
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-xc48-889x-5qmw",
  "modified" : "2026-08-04T17:09:48Z",
  "published" : "2026-08-04T17:09:48Z",
  "aliases" : [ "CVE-2026-69263" ],
  "summary" : "Flowise: CVE-2025-8943 Patch Bypass: npm_config_yes bypasses MCP environment variable blocklist (Unauthenticated RCE)",
  "details" : "## Summary\n\nThe mitigation shipped for CVE-2025-8943 blocks the `-y` and `--yes` flags on `npx` to stop auto-installation of arbitrary packages. That flag filter works. The environment-variable check in the same patch denies only four variable names by exact string match, and `npm` reads its configuration directly from `npm_config_*` environment variables. Setting `npm_config_yes=true` reproduces the `--yes` behaviour the flag filter is meant to prevent, so `npx` auto-installs and executes the named package. The mitigation is fully bypassed.\n\nThis works with the MCP security check enabled (`CUSTOM_MCP_SECURITY_CHECK=true`). On a default Flowise deployment, which ships with no authentication, the result is unauthenticated remote code execution.\n\n## Root cause\n\nThe patch treats this as a flag-filtering problem, but the behaviour gated by `--yes` is also reachable through `npm`'s environment-based configuration. The same is true for the other permitted interpreters, `node` and `python3`. A denylist of variable names cannot enumerate every environment variable that alters execution, so the control is incomplete by construction. The fix is to allowlist (or strip) the environment before it reaches the child process, not to extend the denylist.\n\n## Affected version\n\nFlowise 3.1.1, current as of 2026-03-29.\n\n## Details\n\nValidation happens in `packages/components/nodes/tools/MCP/core.ts`. Two functions run in sequence before any MCP server launches: `validateCommandFlags` and `validateEnvironmentVariables`.\n\n`validateCommandFlags` is thorough. It blocks `-y` and `--yes` along with a comprehensive set of dangerous flags across `npx`, `node`, `python`, `python3`, and `docker`. That part of the patch is sound.\n\nThe gap is in `validateEnvironmentVariables`:\n\n```typescript\nexport const validateEnvironmentVariables = (env: Record<string, any>): void => {\n    const dangerousEnvVars = ['PATH', 'LD_LIBRARY_PATH', 'DYLD_LIBRARY_PATH', 'NODE_OPTIONS']\n    for (const [key, value] of Object.entries(env)) {\n        if (dangerousEnvVars.includes(key)) {\n            throw new Error(`Environment variable '${key}' modification is not allowed`)\n        }\n        if (typeof value === 'string' && value.includes('\\0')) {\n            throw new Error(`Environment variable '${key}' contains null byte`)\n        }\n    }\n}\n```\n\nThe blocklist is a hardcoded four-item array checked by exact match. Any variable not in that list passes through unchecked. `npm_config_yes` is npm's documented mechanism for setting the `yes` config via the environment. Set to `true`, it causes `npx` to auto-install without prompting, which is exactly what the `-y` and `--yes` flag blocks are intended to prevent.\n\n## Proof of concept\n\nThe following MCP server configuration bypasses the patch with `CUSTOM_MCP_SECURITY_CHECK=true`:\n\n```json\n{\n  \"mcpServers\": {\n    \"bypass\": {\n      \"command\": \"npx\",\n      \"args\": [\"malicious-package\"],\n      \"env\": {\n        \"npm_config_yes\": \"true\"\n      }\n    }\n  }\n}\n```\n\nExecution path:\n\n1. `validateCommandFlags` passes, because `args` contains no blocked flags.\n2. `validateEnvironmentVariables` passes, because `npm_config_yes` is not in the four-item blocklist.\n3. `npx` auto-installs and executes the named package with the privileges of the Flowise process.\n\nOn a default deployment with no authentication, any unauthenticated user who can reach the Flowise API can trigger this.\n\n## Additional bypass vectors (same root cause)\n\nThe following variables are also absent from the blocklist and influence execution through the other permitted interpreters:\n\n| Variable | Command | Effect |\n|---|---|---|\n| `npm_config_prefix` | `npx` | Redirects package installation to attacker-controlled path |\n| `npm_config_userconfig` | `npx` | Loads attacker-controlled `.npmrc` configuration |\n| `NODE_PATH` | `node` | Loads modules from attacker-controlled path |\n| `PYTHONPATH` | `python3` | Loads modules from attacker-controlled path |\n| `PYTHONSTARTUP` | `python3` | Executes a file on interpreter startup (interactive sessions only) |\n\n## Impact\n\nFull remote code execution with the privileges of the Flowise process. On default deployments with no authentication, no credentials are required.\n\n## Remediation\n\nStrip the `env` object before passing it to the child process, or replace the name blocklist with an allowlist of explicitly permitted variables.\n\nAdding the known dangerous variables to the blocklist (`npm_config_yes`, `npm_config_prefix`, `npm_config_userconfig`, `NODE_PATH`, `PYTHONPATH`, `PYTHONSTARTUP`) narrows the immediate gap but is a stopgap. Any future permitted interpreter reintroduces the same class of bypass.\n\n## References\n\n- CVE-2025-8943\n- CWE-184: Incomplete List of Disallowed Inputs",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "flowise"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.1.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.1.2"
    }
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "flowise-components"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.1.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.1.2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-xc48-889x-5qmw"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FlowiseAI/Flowise/pull/6471"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FlowiseAI/Flowise/commit/a4c4e4988cded15edf725e762560575b889ae351"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/FlowiseAI/Flowise"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FlowiseAI/Flowise/releases/tag/flowise@3.1.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-184" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-04T17:09:48Z",
    "nvd_published_at" : null
  }
}