Security readout for executives and security teams
Plain-English summary
Flowise versions before 2.1.4 can let an attacker inject configuration during chatflow execution. The reported impact includes remote code execution, server crashes, SSRF, prompt injection, and data or server-variable exposure. This is business-critical for exposed Flowise deployments, but sources do not report active exploitation.
Executive priority
Treat as urgent for any exposed Flowise deployment. The vulnerability has unauthenticated remote code execution potential and high confidentiality, integrity, and availability impact. Prioritize inventory and upgrade, then review logs for signs of misuse.
Technical view
The issue is in the default-enabled overrideConfig option in frontend web integration and backend Prediction API. Without an allow-list and relying on vm2 sandboxing, injected configuration can lead to sandbox escape and code execution. CVSS is 9.8, network exploitable, low complexity, no privileges, no user interaction.
Likely exposure
Flowise deployments before 2.1.4 are the relevant exposure, especially internet-accessible instances using web integrations or the Prediction API. Environments not running Flowise, or running 2.1.4 or later, are not indicated as affected by the provided sources.
Exploitation context
The CVE record marks this as critical and not in CISA KEV. The provided sources do not state active exploitation. Reported effects are self-targeted and do not persist to other users, but compromise of the affected server can still be severe.
Researcher notes
Focus assessment on overrideConfig exposure in Flowise before 2.1.4. Avoid assuming exploitation in the wild; sources do not support that. The advisory notes multiple impacts from the same default-enabled configuration path, including sandbox escape and exfiltration risks.
Mitigation direction
- Identify all Flowise deployments and versions.
- Upgrade vulnerable Flowise instances to 2.1.4 or later, per vendor guidance.
- Review vendor advisory for any configuration-specific recommendations.
- Restrict network access to Flowise interfaces where exposure is not required.
- Monitor for unusual server crashes, outbound requests, or data access patterns.
Validation and detection
- Confirm whether Flowise is deployed in the environment.
- Verify each instance version is 2.1.4 or later.
- Check whether web integration or Prediction API endpoints are exposed.
- Review logs for abnormal prediction requests or unexpected outbound connections.
- Document any compensating access controls around exposed Flowise services.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-58351 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- GHSA Advisory GHSA-5cph-wvm9-45gjCVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: Flowise - Remote Code Execution via overrideConfig ParameterCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.