Flowise OverrideConfig security vulnerability

CRITICAL 9.8CVE-2024-58351 · GHSA-5cph-wvm9-45gj · Published 20/06/2026 · updated 27/10/2026

Package	Affected versions	Patched versions
flowise npm	`< 2.1.4`	`2.1.4`

Description

Impact

Flowise allows developers to inject configuration into the Chainflow during execution through the overrideConfig option. This is supported in both the frontend web integration and the backend Prediction API.

This has a range of fundamental issues that are a major security vulnerability. While this feature is intentional, it should have strong protections added and be disabled by default.

These issues include:

Remote code execution. While inside a sandbox this allows for
Sandbox escape
DoS by crashing the server
SSRF
Prompt Injection, both System and User
Full control over LLM prompts
Server variable and data exfiltration And many many more such as altering the flow of a conversation, prompt exfiltration via LLM proxying etc.

These issues are self-targeted and do not persist to other users but do leave the server and business exposed. All issues are shown with the API but also work with the web embed.

Workarounds

overrideConfig should be disabled by default
overrideConfig should have an explicit allow list of variables that are allowed to be modified. This way the user opts-in to where modifications can be made.
vm2 and any forks of it should be removed as in the authors own words, "fixing the vulnerability seems impossible". The recommended replacement is https://www.npmjs.com/package/isolated-vm

NVD description

Flowise before 2.1.4 allows configuration to be injected into the Chainflow during execution via the overrideConfig option, supported in both the frontend web integration and the backend Prediction API. Because this feature is enabled by default with no allow-list of permitted variables and relies on vm2 for sandboxing, an attacker can abuse it to achieve remote code execution and sandbox escape, denial of service by crashing the server, server-side request forgery, prompt injection, and server variable and data exfiltration. These issues are self-targeted and do not persist to other users.

References

FlowiseAI/Flowise security advisory · WEB
nvd.nist.gov/vuln/detail/CVE-2024-58351 · ADVISORY
FlowiseAI/Flowise · PACKAGE
vulncheck.com/advisories/flowise-remote-code-execution-via-overrideconfig-parameter · WEB

Running one of these products? Scan your site to see whether it exposes a vulnerable version.

Scan my site free

Package

Affected versions

Patched versions

flowise

npm

< 2.1.4

2.1.4

Description

Impact

This has a range of fundamental issues that are a major security vulnerability. While this feature is intentional, it should have strong protections added and be disabled by default.

These issues include:

Remote code execution. While inside a sandbox this allows for
Sandbox escape
DoS by crashing the server
SSRF
Prompt Injection, both System and User
Full control over LLM prompts
Server variable and data exfiltration And many many more such as altering the flow of a conversation, prompt exfiltration via LLM proxying etc.

These issues are self-targeted and do not persist to other users but do leave the server and business exposed. All issues are shown with the API but also work with the web embed.

Workarounds

overrideConfig should be disabled by default
overrideConfig should have an explicit allow list of variables that are allowed to be modified. This way the user opts-in to where modifications can be made.
vm2 and any forks of it should be removed as in the authors own words, "fixing the vulnerability seems impossible". The recommended replacement is https://www.npmjs.com/package/isolated-vm

NVD description