Is CVE-2026-69263 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-69263 being exploited in the wild.

How severe is CVE-2026-69263?

Critical severity, with a CVSS score of 9.8, published 4 August 2026.

Which products and versions are affected?

flowise (npm) <= 3.1.2, SEMVER:introduced=0,fixed=3.1.3; flowise-components (npm) <= 3.1.2, SEMVER:introduced=0,fixed=3.1.3.

Is there a fix for CVE-2026-69263?

Yes. flowise (npm): upgrade to 3.1.3 or later; flowise-components (npm): upgrade to 3.1.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-69263 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-69263?

Check whether you run 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.

CVE-2026-69263: Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, the mitigation for bl

Q: Which products and versions are affected?

flowise (npm) <= 3.1.2, SEMVER:introduced=0,fixed=3.1.3; flowise-components (npm) <= 3.1.2, SEMVER:introduced=0,fixed=3.1.3.

Q: Is there a fix for CVE-2026-69263?

Yes. flowise (npm): upgrade to 3.1.3 or later; flowise-components (npm): upgrade to 3.1.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-69263 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-69263?

Check whether you run 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.

CVE-2026-69263 · Severity: critical · CVSS 9.8 · Published 2026-08-04

Flowise, a tool for building LLM-based applications, contains a vulnerability that allows an attacker to execute arbitrary code on the server. This occurs because a previous security fix could be bypassed by using specific environment variables to force the installation and execution of malicious software. In default installations without authentication, this allows a remote attacker to take full control of the Flowise process and access sensitive data or internal systems.

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

Quick answers

Is CVE-2026-69263 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-69263 being exploited in the wild.
How severe is CVE-2026-69263?: Critical severity, with a CVSS score of 9.8, published 4 August 2026.
Which products and versions are affected?: flowise (npm) <= 3.1.2, SEMVER:introduced=0,fixed=3.1.3; flowise-components (npm) <= 3.1.2, SEMVER:introduced=0,fixed=3.1.3.
Is there a fix for CVE-2026-69263?: Yes. flowise (npm): upgrade to 3.1.3 or later; flowise-components (npm): upgrade to 3.1.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-69263 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-69263?: Check whether you run 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.3 or later
```
npm install flowise@3.1.3
```
flowise-components (npm): upgrade to 3.1.3 or later
```
npm install flowise-components@3.1.3
```

Technical details

This vulnerability is a patch bypass for CVE-2025-8943. While Flowise implemented a blocklist for dangerous command-line flags (like npx --yes), the environment variable validation in 'packages/components/nodes/tools/MCP/core.ts' only checks for a hardcoded list of four variables (PATH, LD_LIBRARY_PATH, DYLD_LIBRARY_PATH, NODE_OPTIONS). An attacker can use 'npm_config_yes=true' to bypass the flag filter, causing npx to auto-install and execute arbitrary packages. Other variables like PYTHONPATH and NODE_PATH are also missing from the blocklist, allowing for module hijacking. This leads to unauthenticated RCE in default deployments where the Flowise API is exposed without credentials. The issue is addressed in version 3.1.3 by improving environment variable handling.

Affected products

FlowiseAI flowise <= 3.1.2
FlowiseAI flowise-components <= 3.1.2

Identifiers

CVE-2026-69263
GHSA-xc48-889x-5qmw

Timeline

2026-07-29: disclosed: Initial disclosure to GitHub Advisory Database
2026-08-04: advisory: GitHub Advisory published
2026-08-04: patched: Fix released in version 3.1.3

References

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