High (AgentArmorHQ estimate)Remote code execution

Flowise: CVE-2025-8943 Patch Bypass: npm_config_yes bypasses MCP environment variable blocklist (Unauthenticated RCE)

Product
flowise
CVE
CVE-2026-69263
Affected
flowise <= 3.1.2
Fixed in
3.1.3

Last verified against sources: October 26, 2026

Am I affected?

flowise: affected flowise <= 3.1.2. Fixed in 3.1.3.

  • Check your version: run npm ls flowise. Versions <= 3.1.2 of flowise are affected. [1]
  • Check your version: run npm ls flowise-components. Versions <= 3.1.2 of flowise-components are affected. [1]

What to do now

  1. Upgrade to the fixed version: run npm install flowise@3.1.3 (first patched version 3.1.3). [1]
  2. Upgrade to the fixed version: run npm install flowise-components@3.1.3 (first patched version 3.1.3). [1]
  3. Strip the env object before passing it to the child process, or replace the name blocklist with an allowlist of explicitly permitted variables. [1]
  4. 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. [1]

General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.

Discuss this incident

What happened

  • The mitigation shipped for CVE-2025-8943 blocks the -y and --yes flags on npx to stop auto-installation of arbitrary packages. [1]
  • 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. [1]
  • 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. [1]
  • The mitigation is fully bypassed. [1]

Impact

  • Full remote code execution with the privileges of the Flowise process. [1]
  • On default deployments with no authentication, no credentials are required. [1]
  • On a default Flowise deployment, which ships with no authentication, the result is unauthenticated remote code execution. [1]

What was done

  • npm/flowise affected <= 3.1.2 patched 3.1.3. [1]
  • The fix is to allowlist (or strip) the environment before it reaches the child process, not to extend the denylist. [1]
  • Strip the env object before passing it to the child process, or replace the name blocklist with an allowlist of explicitly permitted variables. [1]

Sources

  1. GHSA-xc48-889x-5qmw — GitHub Advisory Database

Every statement above was checked against these sources before publishing. Spotted an error? Tell us and we will correct it with a dated note.

Share advisory brief with your team

Copy a plain-text summary for Slack, GitHub issues, or team security channels.

Brief
[CVE-2026-69263] Flowise: CVE-2025-8943 Patch Bypass: npm_config_yes bypasses MCP environment variable blocklist (Unauthenticated RCE)
Product: flowise | Affected: flowise <= 3.1.2 | Fixed in: 3.1.3
Summary: The mitigation shipped for CVE-2025-8943 blocks the `-y` and `--yes` flags on `npx` to stop auto-installation of arbitrary packages.
Source & remediation on AgentArmorHQ: https://agentarmorhq.com/incidents/2026/08/cve-2026-69263-flowise
Was this page useful?

Corrections

Report an error or request a correction. We review requests within 5 business days and add a dated correction note.

10 to 2,000 characters. A link to a source helps. Stored as plain text.

Discussions for CVE-2026-69263

Ask questions or share configuration tips. Governed by our Community Rules & Terms.

No posts match this filter yet.

Be the first to ask a question or share a working tip.

Check before you install

Paste a package name or a GitHub link and get a clear answer in seconds: Block, Review or No known issues. No account needed.

Check a package

Questions? Contact us