Flowise CVE-2025-59528 Exploited via CustomMCP JavaScript Injection

Summary
VulnCheck reportedly detected exploitation of Flowise CVE-2025-59528, which enables code execution through unsafe CustomMCP configuration handling. The flaw is fixed in versions 3.0.6 and 3.1.1; the number of vulnerable public instances is unclear.
Key points
- CVE-2025-59528 involves unsafe evaluation of user-supplied mcpServerConfig in Flowise’s CustomMCP node, enabling arbitrary JavaScript execution.
- VulnCheck’s Canary network reportedly detected exploitation; the observed activity so far originated from a single Starlink IP, according to VulnCheck.
- VulnCheck estimated that 12,000–15,000 Flowise instances were publicly reachable, but the article says the number vulnerable to CVE-2025-59528 is unclear.
- The article reports that the issue was fixed in Flowise 3.0.6; version 3.1.1 also includes the fix.
- The article says CVE-2025-8943 and CVE-2025-26319 are also being actively exploited and are listed in VulnCheck’s KEV catalog.
- Users are advised to upgrade to at least Flowise 3.0.6 and remove unnecessary public internet access.
Article Details
- Vulnerability Types
- Remote code execution
- Arbitrary JavaScript code injection
- Severity
- Critical; CVSS 10
- Exploitation Status
- active
- Exploit Availability
- unknown
- Patch Status
- available
- Workarounds
- Remove Flowise instances from the public internet if external access is not required.
MITRE ATT&CK
CVE
CVE-2025-26319Flowiseai · FlowiseAdditional Flowise vulnerabilities (CVE-2025-8943 and CVE-2025-26319) are also being actively exploited and listed in VulnCheck’s KEV.CVE-2025-59528FlowiseAI · FlowiseA critical remote code execution vulnerability in Flowise (CVE-2025-59528) is being actively exploited, allowing attackers to inject and execute arbitrary JavaScript via the CustomMCP mcpServerConfig setting.CVE-2025-8943Flowiseai · FlowiseAdditional Flowise vulnerabilities (CVE-2025-8943 and CVE-2025-26319) are also being actively exploited and listed in VulnCheck’s KEV.
