Loading vulnerability…
CVE-2026-58057 is an arbitrary code execution vulnerability in Flowise before version 3.1.3 affecting validation of Custom MCP stdio environment variables on Windows. The application enforces a denylist for dangerous environment variable names, including NODE_OPTIONS, but performs the comparison in a case-sensitive manner. Because Windows treats environment variable names as case-insensitive, an authenticated user can supply an alternate casing such as node_options to bypass the denylist. If the attacker has permission to configure a Custom MCP node, they can inject NODE_OPTIONS with a --require option and cause attacker-controlled code to be loaded and executed in the Flowise server process context.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
Repository contains a standalone Python exploit for authenticated RCE against Flowise via CVE-2026-58057. Structure is minimal: LICENSE, README.md, requirements.txt, and a single main script exploit.py. The Python script is the operational entry point and includes dependency bootstrapping for requests/urllib3, custom colored logging, argument-driven execution, and a FlowiseExploit class for interacting with the target. Based on the README and visible code, the exploit authenticates to a Flowise instance, abuses vulnerable case-sensitive validation by supplying lowercase 'node_options', and causes Node.js to load a malicious JavaScript loader through '--require' when a Custom MCP stdio node executes. The exploit is not merely a detector; it is intended to achieve code execution and then run one of several post-exploitation payloads. Exposed capabilities include reverse shell, bind shell, arbitrary command execution, file upload, persistence installation, system information collection, credential dumping, screenshot capture, and keylogging. Fingerprintable artifacts include the Flowise API version endpoint '/api/v1/version', the loader filename 'malicious-loader.js', and several expected output files on the target such as 'exec_output_*.txt', 'system_info_*.json', 'creds.txt', 'screenshot.png', and 'keystrokes.log'. The exploit also references persistence via Startup folder, Registry, and Scheduled Task. Overall, this is a purpose-built, standalone authenticated web/network exploit with operational payload support rather than a simple proof of concept.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.