External risk intelligence

Flowise Record Manager and Agent Memory Arbitrary Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.0)

CVE-2026-69251

Flowise is a web-based application designed for building and managing large language model flows. Such applications are commonly deployed as internet-facing web services or APIs to allow users and systems to interact with the interface and the LLM workflows, making the application's management and configuration endpoints frequently accessible from the network.

Code Injection

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 CVE involves a vulnerability in Flowise, a tool used for building large language model applications, where an authenticated user could execute arbitrary code on the server. This could occur if a user can manipulate certain configuration settings to load local JavaScript files.

  • Code execution risk in Flowise application building tool.
  • Important for leaders to ensure their AI development tools are secure.
  • Confirm relevance and potential exposure within your AI initiatives.

Attack Path

How an attacker could exploit the issue

An authenticated user can exploit this vulnerability by providing a malicious JavaScript payload within the `additionalConfig` parameter of specific Flowise nodes, such as the record manager or agent memory components. This allows the user to load local JavaScript files, leading to arbitrary code execution on the server.

  • Authenticated access required.
  • Arbitrary JavaScript file loading.
  • Server-side code execution risk.

Live Threat

Current exploitation, exposure, and threat context

An authenticated user could execute arbitrary code on the server when Flowise's record manager or agent memory nodes are configured with malicious TypeORM DataSource options. This could affect the server's operation and any data it processes.

  • Server-side code execution.
  • Malicious configuration input.
  • Compromised service operation.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Flowise application's record manager and agent memory nodes are susceptible to arbitrary code execution by authenticated users. Responsibility for this system likely falls to the platform or application owners who manage the Flowise deployment. The first practical step is to identify all instances of Flowise, determine their reachability and business criticality, and then engage the accountable owners to plan remediation based on the assessed risk.

  • Platform or application owners should own this.
  • Verify Flowise deployment reachability and criticality.
  • Plan remediation with accountable owners.

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 and what is it used for?

Flowise is a platform that provides a visual, drag-and-drop interface for developers and engineers to build and manage workflows for large language models. It simplifies the orchestration of LLM-based applications by allowing users to connect various components, such as memory nodes and record managers, to handle data flow and state.

What does CVE-2026-69251 mean for the software?

This vulnerability is classified as CWE-94, or Improper Control of Generation of Code. In CVE-2026-69251, the software fails to properly restrict configuration inputs in specific nodes. This allows a user to supply malicious settings that instruct the server to load and execute arbitrary JavaScript files, effectively letting them run unauthorized code on the host system.

How is this arbitrary code execution triggered?

An attacker triggers this by manipulating the 'additionalConfig' input field within affected record manager or agent memory nodes. The flaw is not triggered by standard usage of these nodes; it requires an authenticated user to specifically inject paths to malicious JavaScript files via TypeORM DataSource options. Without the ability to modify these configuration fields, the underlying code loading mechanism is not activated.

Is my Flowise instance at risk?

If you are running a version prior to 3.1.3, your instance is vulnerable. Halo Surface Signal identifies this as a 'Likely' concern because Flowise is frequently deployed as an internet-facing web service or API to support LLM workflows, which can make these management endpoints accessible to attackers across the network.

What should I do to secure my environment?

Your first step is to identify all Flowise deployments in your infrastructure and verify their current version. Since this is resolved in version 3.1.3, you should prioritize upgrading to this release or newer. While planning the upgrade, assess the accessibility of your instances and ensure that access to configuration interfaces is restricted to authorized users only.

References