Loading vulnerability…
CVE-2025-8943 is an OS command injection vulnerability in Flowise Custom MCP functionality affecting Flowise versions earlier than 3.0.1. The Custom MCP feature launches local MCP servers by executing operating-system commands, including through utilities such as npx. The node-load-method/customMCP API route accepts attacker-controlled MCP server command and argument configuration that can be used to invoke arbitrary unsandboxed commands. Flowise deployments were unauthenticated by default unless authentication was explicitly configured, and the product lacked granular role-based authorization, allowing remote unauthenticated attackers to reach the command-execution functionality.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (3 hidden).
Small repository containing a documentation-heavy proof of concept for CVE-2026-69263, a Flowise patch-bypass leading to RCE. Structure is minimal: LICENSE, README.md, and poc.json. There is no executable exploit script; the core artifact is poc.json, an MCP server configuration that sets command=npx, args=["cowsay"], and env.npm_config_yes=true. According to the README, this bypasses Flowise's denylist-based MCP security checks when CUSTOM_MCP_SECURITY_CHECK=true, because the blocked flags are not present and the environment variable is not denylisted. As a result, npx auto-installs and executes the specified package, demonstrating arbitrary execution with the privileges of the Flowise process. The README further explains likely exploitation conditions: vulnerable Flowise 3.1.1, fixed in 3.1.3, and reachable Flowise API access, potentially unauthenticated on default deployments. It also documents related environment-variable bypass avenues (npm_config_prefix, npm_config_userconfig, NODE_PATH, PYTHONPATH, PYTHONSTARTUP), indicating the broader root cause is incomplete filtering of dangerous interpreter/package-manager environment variables rather than a single hardcoded bypass.
This repository contains a single Metasploit module (modules/exploits/multi/http/flowise_custommcp_rce.rb) that exploits a remote code execution vulnerability (CVE-2025-8943) in Flowise versions >=2.2.7-patch.1 and <3.0.1. The exploit targets the /api/v1/node-load-method/customMCP HTTP endpoint, which allows arbitrary command execution when the 'x-request-from: internal' header is set. The module supports both Unix/Linux and Windows targets and can deliver any Metasploit command payload. Authentication is only required if the target Flowise instance is configured with Basic Auth; otherwise, the exploit works unauthenticated. The module is weaponized, providing full remote code execution capabilities via the Metasploit framework. The repository is structured as a single Ruby file, following standard Metasploit module conventions.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Flowise RCE vulnerability where unvalidated MCP server configuration can reach a shell.
An earlier Flowise vulnerability whose mitigation was bypassed by CVE-2026-69263.
A remote code execution vulnerability in Flowise, referenced as part of Metasploit module PRs.
A Flowise-related vulnerability that the content says is being actively exploited and is included in VulnCheck's Known Exploited Vulnerabilities catalog, but no technical details are provided.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.