Loading story…
Flowise disclosed and fixed a cluster of high-severity vulnerabilities in versions prior to 3.1.0, including multiple paths to remote code execution. The most serious issues affect the platform's CSV and Airtable agent components, where unsanitized user input or LLM-generated Python code could be evaluated without proper sandboxing. Advisories for CVE-2026-41137, CVE-2026-41264, CVE-2026-41138, and CVE-2026-41265 describe authenticated and unauthenticated attack paths that let attackers inject malicious payloads through chatflows or agent inputs and execute code on the Flowise server, with potential impact to confidentiality, integrity, and availability.
Flowise 3.1.0 also addresses non-RCE flaws that could expose multi-tenant environments and consume third-party service credits. CVE-2026-41279 affects the unauthenticated text-to-speech endpoint at POST /api/v1/text-to-speech/generate, which could accept an arbitrary credentialId and use decrypted stored credentials such as OpenAI or ElevenLabs API keys to generate speech, enabling API credit abuse. In Flowise Cloud, CVE-2026-41267 allows improper mass assignment during account registration, letting unauthenticated attackers inject server-managed fields and manipulate organization associations, ownership metadata, timestamps, and role mappings across tenants. Organizations running Flowise or Flowise Cloud should upgrade to 3.1.0 and review exposed chatflows, stored credentials, and tenant registration controls.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
5 events from the most recent confirmed update back to the earliest known activity.
On April 23, 2026, CVE records were received or updated to add descriptions, CVSS vectors, CWE mappings, and GitHub advisory references. The content explicitly notes update activity for CVE-2026-41137 and CVE-2026-41265 on that date.
Several vulnerabilities affecting Flowise and Flowise Cloud were publicly disclosed, including CVE-2026-41137, CVE-2026-41138, CVE-2026-41264, CVE-2026-41265, CVE-2026-41267, and CVE-2026-41279. The disclosures documented authenticated and unauthenticated RCE paths, tenant-association manipulation, and API credit abuse via stored credentials.
A critical Flowise vulnerability, CVE-2026-41273, was publicly disclosed affecting versions prior to 3.1.0. The flaw allowed unauthenticated attackers to access public chatflow configuration endpoints, extract OAuth credential identifiers, and obtain valid OAuth 2.0 access tokens for unauthorized access to connected third-party services.
Flowise fixed several security flaws in version 3.1.0, including CSVAgent and Airtable agent remote code execution issues, an unauthenticated text-to-speech credential abuse flaw, and a Flowise Cloud account registration mass-assignment issue. All referenced advisories describe affected versions as prior to 3.1.0.
Trend Micro's Zero Day Initiative reported CVE-2026-41265, an unauthenticated remote code execution flaw in Flowise's Airtable_Agent component, to the vendor through coordinated disclosure. The issue allowed arbitrary Python code execution via improper validation in the run method and was credited to Dre Cura and Nicholas Zubrisky.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
9 references tracked. Mallory keeps watching after this page renders.
sentinelone.com
Open sourcecvefeed.io
Open sourcecvefeed.io
Open sourcecvefeed.io
Open sourcecvefeed.io
Open sourcecvefeed.io
Open sourcecvefeed.io
Open sourcecvefeed.io
Open sourcezerodayinitiative.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Threat actors are actively exploiting **CVE-2025-59528**, a **CVSS 10.0** remote code execution flaw in the open-source AI platform **Flowise**. The bug affects Flowise versions through **3.0.5** and stems from the `CustomMCP` node unsafely passing user-controlled input into JavaScript execution, allowing attackers with an API token to run arbitrary code with full **Node.js** runtime privileges. Researchers said the issue can be triggered remotely via a crafted HTTP `POST` request without user interaction, leading to operating system command execution, filesystem access, sensitive data theft, and full system compromise. Security researchers observed in-the-wild exploitation originating from a single **Starlink IP address**, while warning that roughly **12,000 to 15,000** internet-exposed Flowise instances sharply expand the attack surface for opportunistic attacks. Flowise disclosed the vulnerability in 2025, credited researcher **Kim SooHyun**, and patched the flaw in **version 3.0.6**. The incident marks the third Flowise vulnerability reported as exploited in the wild after **CVE-2025-8943** and **CVE-2025-26319**, increasing pressure on organizations to upgrade immediately and limit public exposure of Flowise APIs.
Jun 29, 2026
A critical remote code execution vulnerability, tracked as CVE-2025-61913, has been identified in Flowise, a drag-and-drop user interface for building customized large language model flows. The flaw exists in versions prior to 3.0.8 and is caused by insufficient restrictions in the WriteFileTool and ReadFileTool components, which fail to properly validate file path access. This oversight allows authenticated attackers to read and write arbitrary files to any location on the file system, significantly increasing the risk of remote code execution. The vulnerability has been assigned a CVSS score of 10.0, indicating its maximum severity and potential for exploitation. According to security advisories, the issue can be exploited remotely, making it a high-priority concern for organizations using affected versions of Flowise. The vulnerability was publicly disclosed on October 8, 2025, and a security update was released in version 3.0.8 to address the issue. Attackers leveraging this flaw could gain unauthorized access to sensitive files, modify system configurations, or deploy malicious payloads, potentially leading to full system compromise. The vulnerability affects all installations of Flowise prior to the patched version, though the exact list of affected products and vendors has not been fully enumerated. Security researchers emphasize the critical nature of the flaw due to the ease of exploitation and the broad impact on confidentiality, integrity, and availability. Organizations are strongly advised to upgrade to Flowise version 3.0.8 or later to mitigate the risk. The vulnerability was reported through GitHub security advisories, highlighting the importance of monitoring open-source project disclosures. No evidence of active exploitation in the wild has been reported as of the disclosure date, but the public availability of technical details increases the urgency for remediation. The flaw underscores the risks associated with insufficient input validation in file handling components of web applications. Security teams should review their deployment of Flowise and apply the necessary patches without delay. In addition to patching, organizations should audit access logs for signs of suspicious file operations that could indicate attempted exploitation. The incident serves as a reminder of the critical need for secure coding practices and regular vulnerability assessments in software development.
Jun 29, 2026
Researchers disclosed **CVE-2026-40933**, a critical remote code execution flaw in self-hosted **Flowise** deployments tied to the platform’s Custom **MCP** support over `stdio`. The issue lets an authenticated attacker execute arbitrary OS commands with the privileges of the Flowise process by supplying a malicious MCP server configuration, either directly or by embedding it in a shared chatflow. In the demonstrated one-click scenario, importing the crafted chatflow alone can trigger server-side command execution when Flowise enumerates available MCP actions, before any save or run step. **Flowise Cloud** is not affected because `stdio` MCP is disabled, but open-source and enterprise self-hosted deployments are vulnerable by default. Reporting on the flaw said Flowise’s initial mitigation—blocking risky flags for allowlisted commands—does not fix the underlying problem because the feature still launches user-controlled processes, and researchers showed it can be bypassed through environment variables. Recommended defenses include upgrading to **Flowise 3.1.0**, limiting who can add or import MCP configurations, isolating Flowise from sensitive internal systems, and disabling `stdio` MCP unless it is strictly required by setting: ```bash CUSTOM_MCP_PROTOCOL=sse ``` The disclosures also warn that the bug reflects a broader architectural and supply-chain risk for agentic AI platforms that expose unsandboxed `stdio`-based MCP configuration to lower-trust users or untrusted artifacts.
Jun 29, 2026