CVE-2024-58351: Flowise Code Injection via overrideConfig
CVE-2024-58351 affects Flowise before 2.1.4 and allows configuration to be injected into the Chainflow during execution through the overrideConfig option, in both the web integration and the Prediction API. The description reports possible remote code execution, sandbox escape, denial of service, SSRF and data exfiltration, and states that the feature is enabled by default. The record contains no confirmed exploitation and no structured affected or fixed version data, so upgrade planning should rely on the cited advisories.
Overview
CVE-2024-58351 is a code injection weakness (CWE-94) in Flowise. According to the record description, configuration can be injected into the Chainflow during execution through the overrideConfig option, which is supported in both the frontend web integration and the backend Prediction API.
Impact
The description states that the feature is enabled by default, has no allow-list of permitted variables, and relies on vm2 for sandboxing. It lists 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 as possible outcomes. It also says these issues are self-targeted and do not persist to other users.
- The CVSS 3.1 base score is 9.8 (critical), as provided by the CNA VulnCheck.
- A CVSS 4.0 score of 9.3 is also provided by VulnCheck.
Affected products and versions
The description refers to Flowise before 2.1.4. The structured affected and fixes lists in the record are empty, so no further version ranges or fixed builds are confirmed here. Consult the GitHub advisory and the VulnCheck advisory for authoritative version data.
Exploitation status
The CISA KEV catalog does not list this CVE (kev.listed is false). No confirmed exploitation in the wild appears in the sources consulted for this analysis. EPSS and SSVC data are not present in the record.
Remediation and mitigation
- Inventory Flowise deployments and identify any running a version earlier than 2.1.4.
- Plan an upgrade to 2.1.4 or later. The description's version boundary suggests that release addresses the issue, but confirm this against the GitHub advisory.
- Until upgraded, limit network exposure of the web integration and Prediction API, and restrict who can supply overrideConfig input.
- Review whether the default-enabled behaviour can be disabled or constrained in your configuration.
Detection guidance
- Review application and API logs for requests carrying overrideConfig parameters from unexpected sources.
- Monitor for unexpected server process crashes, unusual outbound connections from the Flowise host, and unexpected access to server environment data.
Limitations of the available information
The record has no structured affected products, no fixed version list, no EPSS or SSVC data, and a source status of Deferred. The vendor advisory text was not available beyond the description. Remediation statements are inferences unless tied to a cited source.
Frequently asked questions
Which Flowise versions does CVE-2024-58351 concern?
The record description refers to Flowise before 2.1.4. The structured affected and fixed version lists are empty, so check the GitHub and VulnCheck advisories for authoritative data.
Is this CVE known to be actively exploited?
The CISA KEV catalog does not list it in this record, and no confirmed exploitation appears in the sources consulted. This is not a guarantee that exploitation does not occur.
What should administrators do first?
Identify deployments running versions before 2.1.4, plan an upgrade, and limit network exposure of the web integration and Prediction API until the upgrade is complete.
This analysis was drafted with AI assistance from verified source data and automatically checked against it.