Is CVE-2026-40933 exploited in the wild?

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

How severe is CVE-2026-40933?

Critical severity, with a CVSS score of 9.9, published 21 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-40933?

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-40933 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-40933?

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.

CVE-2026-40933: Flowise Flowise authenticated RCE in MCP Adapters

Q: 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.

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

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.

Q: How is CVE-2026-40933 attacked?

It is attacked over the network, in a software library.

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

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.

CVE-2026-40933 · Severity: critical · CVSS 9.9 · Published 2026-04-21

Flowise is an open-source tool used to build customized AI workflows and applications. A security vulnerability in its Model Context Protocol (MCP) adapter allows an authenticated user to execute arbitrary commands on the server hosting the application. This could lead to a complete system takeover, unauthorized access to sensitive AI models, or theft of corporate data.

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

Quick answers

Is CVE-2026-40933 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-40933 being exploited in the wild.
How severe is CVE-2026-40933?: Critical severity, with a CVSS score of 9.9, published 21 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-40933?: 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-40933 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-40933?: 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

An OS command injection vulnerability (CWE-78) exists in Flowise due to improper neutralization of special elements in the Model Context Protocol (MCP) adapter. While the application implements some sanitization checks (such as validateCommandInjection), these can be bypassed by providing "safe" commands like 'npx' combined with malicious arguments (e.g., '-c'). An authenticated attacker with access to the canvas configuration can add a custom MCP using the stdio transport to execute arbitrary commands on the underlying operating system. The vulnerability is fixed in version 3.1.0.

Affected products

FlowiseAI flowise <= 3.0.13
FlowiseAI flowise-components <= 3.0.13

Identifiers

CVE-2026-40933
GHSA-c9gw-hvqq-f33r

Timeline

2026-04-15: disclosed
2026-04-16: advisory: GHSA-c9gw-hvqq-f33r published
2026-04-16: patched: Version 3.1.0 released

References

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