External risk intelligence

Flowise Sandbox Escape via vm2 Vulnerability Allows Arbitrary Code Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.0)

CVE-2026-73602

Flowise is a low-code platform for building LLM applications, which is commonly deployed as a web-based interface or API service. These services are frequently exposed to the internet to enable remote access for users and integration with external applications, making the web interface and associated API endpoints common internet-facing attack surfaces.

Path Traversal

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory details a critical vulnerability in Flowise, a platform for building AI applications. The issue allows authenticated users to potentially execute malicious code by bypassing security measures within a JavaScript sandbox. This could enable unauthorized access and control over the platform and its connected systems.

  • Allows code execution via sandbox bypass.
  • Matters for maintaining platform integrity.
  • Confirm relevance and potential exposure.

Attack Path

How an attacker could exploit the issue

An authenticated user can exploit a vulnerability in the vm2 JavaScript sandbox by crafting a malicious String object. This object can bypass path traversal defenses, allowing the attacker to load and execute arbitrary JavaScript code from the document store, effectively escaping the sandbox.

  • Authenticated access required.
  • Bypasses sandbox path traversal checks.
  • Leads to arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an authenticated user to execute arbitrary code outside of the intended sandbox environment, potentially impacting the integrity and availability of the affected system. The exploit involves bypassing security checks to load and run malicious JavaScript files.

  • System integrity and availability.
  • Authenticated user can bypass sandbox controls.
  • Arbitrary code execution in the document store.

Operational Fix

Recommended remediation, mitigation, and detection steps

The vulnerability in Flowise affects authenticated users and allows for arbitrary code execution, indicating that application owners and platform teams responsible for the Flowise deployment should take the lead. The immediate practical step is to identify all Flowise instances, determine their exposure and criticality, and then engage with vendor management if a patched version is available or plan necessary remediation based on assessed risk.

  • Application owners should lead remediation efforts.
  • Verify external reachability and asset criticality.
  • Coordinate with vendor management for updates.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Flowise?

Flowise is a low-code software platform designed for building applications powered by Large Language Models (LLMs). It provides a visual interface and API services that allow developers and users to construct complex AI workflows, integrate them with various tools, and manage data within the application environment.

What is the vulnerability in CVE-2026-73602?

This vulnerability is classified as Improper Neutralization of Directives in Dynamically Evaluated Code (CWE-95). It represents a sandbox escape where the software's vm2 JavaScript environment fails to properly isolate execution. By manipulating specific validation checks, an attacker can break out of this restricted container to run unauthorized code on the underlying host system.

How does an attacker trigger this sandbox escape?

An attacker triggers the bug by using an authenticated account to submit a specially crafted String object. This object contains a deceptive match function that tricks the system into bypassing path traversal protections. Notably, this does not occur through standard user interaction; it requires the ability to interact with the platform's document store logic to load external files.

Why is this a concern according to Halo Surface Signal?

Halo Surface Signal notes that Flowise is often deployed as a web-based or API service, which frequently places these platforms on the internet to support remote users and integrations. Because this creates a broad, internet-facing attack surface, the risk is elevated for any organization that has enabled external access to their Flowise instances.

Do I need to update my Flowise installation?

Yes, if you are running a version earlier than 3.1.3, you are affected. The priority is to inventory your instances to determine which are reachable by users, then coordinate with your technical team to apply the available vendor update. Because this flaw allows for arbitrary code execution, ensuring your deployment is patched is a critical step for maintaining system integrity.

References