CVE-2024-58351
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFlowise 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceFlowise before 2.1.4 has a default-enabled overrideConfig feature in both frontend web integration and backend Prediction API that allows injecting configuration into Chainflow during execution. The feature uses vm2 for sandboxing (which has known sandbox escape vulnerabilities) and has no allow-list of permitted variables, enabling RCE, sandbox escape, DoS, SSRF, prompt injection, and data exfiltration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Flowise versionLocate the Flowise installation and check the version number in package.json, or run 'npm list flowise' or check the Docker image tag if containerizedAffected if The installed version is before 2.1.4
-
Locate overrideConfig usage in codeSearch the codebase for 'overrideConfig' string in JavaScript/TypeScript source files, API route handlers, and configuration files to determine if the feature is implementedAffected if overrideConfig is found and enabled in the codebase
-
Detect vm2 dependencyCheck package.json for 'vm2' in dependencies or run 'npm list vm2' to see if vm2 is installedAffected if vm2 is present as a dependency
-
Inspect configuration allow-listingSearch for any allow-list, whitelist, or permitted configuration variable definitions related to overrideConfig in configuration or source filesAffected if No allow-list exists for permitted configuration variables in overrideConfig implementation
A user is affected if running Flowise version before 2.1.4 with the overrideConfig feature implemented and vm2 present in dependencies without a configuration variable allow-list.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedDisable the overrideConfig feature by default, implement an explicit allow-list of permitted configuration variables, and replace vm2 with a more secure sandboxing solution.
Flowise 2.1.4
- Upgrade Flowise to version 2.1.4 or later by following the official upgrade documentation for your deployment method
- After upgrading, verify the overrideConfig feature behavior to ensure it is either disabled by default or properly allow-listed
- Restart the Flowise service to apply the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation20.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-58351 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-58351 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data