CVE-2024-58351: Flowise Flowise OverrideConfig Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-5cph-wvm9-45gj
CWE-15
Published
Advisory Summary

CVE-2024-58351 is a HIGH flowise overrideconfig security vulnerability vulnerability (CWE-15: External Control of System or Configuration Setting) affecting Flowise libraries in the npm ecosystem. The issue involves flowise overrideconfig security vulnerability. Remediation is available by upgrading affected packages to version 2.1.4.

CVE-2024-58351 at a Glance

CVE Identifier CVE-2024-58351
GHSA Identifier GHSA-5cph-wvm9-45gj
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-15: External Control of System or Configuration Setting
Affected Product Flowise
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2024-58351

To remediate this vulnerability, upgrade all affected Flowise dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

flowise fixed: 2.1.4
npm install flowise@2.1.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls flowise

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2024-58351, inspect your project dependencies using npm:

npm ls flowise

Analyze the terminal output to locate any version of Flowise in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.1.4), your application is affected.

Note: The npm ls flowise command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-15: External Control of System or Configuration Setting, where one or more system settings or configuration elements can be externally controlled by a user. In Flowise, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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: 1. Remote code execution. While inside a sandbox this allows for 1. Sandbox escape 2. DoS by crashing the server 3. SSRF 2. Prompt Injection, both System and User 1. Full control over LLM prompts 2. 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

CVE-2024-58351 Affected Flowise Versions

1 component(s)
Fixed Versions:
2.1.4
Product / Package Ecosystem Affected Versions Fixed Version
flowise
npm
< 2.1.4
2.1.4

References

Frequently Asked Questions

What is CVE-2024-58351?
CVE-2024-58351 is a security vulnerability in Flowise involving Flowise OverrideConfig security vulnerability under CWE-15: External Control of System or Configuration Setting.
Which Flowise versions are affected?
Affected versions include releases prior to 2.1.4 across affected packages: flowise.
What version fixes CVE-2024-58351?
Upgrading to 2.1.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is flowise affected?
Yes, flowise is affected in releases prior to 2.1.4. Upgrade your dependency to 2.1.4 or later.
What CWE is associated with CVE-2024-58351?
CVE-2024-58351 is classified under CWE-15: External Control of System or Configuration Setting (One or more system settings or configuration elements can be externally controlled by a user.).
How can I check npm dependencies for CVE-2024-58351?
Run the dependency tree command: 'npm ls flowise'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5cph-wvm9-45gj",
  "modified" : "2026-09-14T17:15:31Z",
  "published" : "2024-11-21T22:21:03Z",
  "aliases" : [ "CVE-2024-58351" ],
  "summary" : "Flowise OverrideConfig security vulnerability",
  "details" : "### Impact\nFlowise 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. \n\nThis has a range of fundamental issues that are a **major** security vulnerability. \nWhile this feature is intentional, it should have strong protections added and be disabled by default. \n\nThese issues include: \n1. Remote code execution. While inside a sandbox this allows for\n  1. Sandbox escape \n  2. DoS by crashing the server\n  3. SSRF\n2. Prompt Injection, both System and User\n  1. Full control over LLM prompts\n  2. Server variable and data exfiltration\nAnd many many more such as altering the flow of a conversation, prompt exfiltration via LLM proxying etc.\n\nThese issues are self-targeted and do not persist to other users but do leave the server and business exposed. \nAll issues are shown with the API but also work with the web embed.\n\n### Workarounds\n- `overrideConfig` should be disabled by default\n- `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. \n- `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",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "flowise"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.1.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-5cph-wvm9-45gj"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-58351"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/FlowiseAI/Flowise"
  }, {
    "type" : "WEB",
    "url" : "https://www.vulncheck.com/advisories/flowise-remote-code-execution-via-overrideconfig-parameter"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-15" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-11-21T22:21:03Z",
    "nvd_published_at" : null
  }
}