SardinhaNews

CVE-2025-59528

Critical🧨 Metasploit📦 Exploit-DB🔍 NucleiSSVC AttendBDU · public exploit

Published: 09/22/2025 · Modified: 10/18/2026

CVSS 3.1ⓘ10.0
EPSSⓘ91.7%
VPR (Tenable)8.0

Description

Flowise is a drag & drop user interface to build a customized large language model flow. In version 3.0.5, Flowise is vulnerable to remote code execution. The CustomMCP node allows users to input configuration settings for connecting to an external MCP server. This node parses the user-provided mcpServerConfig string to build the MCP server configuration. However, during this process, it executes JavaScript code without any security validation. Specifically, inside the convertToValidJSONString function, user input is directly passed to the Function() constructor, which evaluates and executes the input as JavaScript code. Since this runs with full Node.js runtime privileges, it can access dangerous modules such as child_process and fs. This issue has been patched in version 3.0.6.

Exploitation

Requires: network access · Does not require: authentication, user interaction, special target conditions

How it is exploited

Exploitation method

  • The attacker sends an HTTP request to the customMCP endpoint (/api/v1/node-load-method/customMCP) of the Flowise instance.
  • In the mcpServerConfig parameter, the attacker supplies a specially crafted string.
  • The convertToValidJSONString function passes user input directly to the Function() constructor, which evaluates and executes the content as JavaScript code.
  • The code runs with full Node.js runtime privileges, allowing access to dangerous modules such as child_process and fs.
  • This results in remote arbitrary code execution on the server.

Am I affected? (applicability)

  • The Flowise instance is running versions >= 2.2.7-patch.1 and < 3.0.6 (including 3.0.5).
  • The /api/v1/node-load-method/customMCP endpoint is reachable over the network.
  • For versions < 3.0.1: the FLOWISE_USERNAME and FLOWISE_PASSWORD environment variables are not configured (unauthenticated exploitation).
  • For versions >= 3.0.1: authentication via FLOWISE_EMAIL and FLOWISE_PASSWORD is required due to JWT token verification.
  • The CustomMCP node is available and processes user input.

Does not require: authentication, user interaction, special target conditions.

Mitigation and detection

  • Update to version 3.0.6 or later (vendor fix).
  • Restrict network access to the /api/v1/node-load-method/customMCP endpoint.
  • Use the available Nuclei template for automated detection of the vulnerability.

Impact if exploited

Remote code execution with full Node.js privileges — complete control of the Flowise server.

Confidentiality: highIntegrity: highAvailability: high

Also affects components beyond the vulnerable one.

Community reports (unverified): exploitation 12 · PoC 20

References and technical detail

The “Requires/Does not require” line and the confidentiality, integrity and availability impact come from the official CVSS vector. Method, applicability and mitigation are an automatic summary of the NVD description, public exploitation sources (Metasploit, Nuclei, Exploit-DB) and the CVE record via CIRCL (advisories and fixed version), linked under “References and technical detail”. Community reports come from CIRCL sightings and are unverified.

Exploitation probability (EPSS) over time

07/13/202608/24/202611/01/202611/13/2026

Affected products

  • flowiseai · flowise

Weakness type (CWE)

In the news

Timeline on SardinhaNews

References