Summary
Workarounds
overrideConfigshould be disabled by defaultoverrideConfigshould 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.vm2and 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
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-5CPH-WVM9-45GJ? GHSA-5CPH-WVM9-45GJ is a high-severity security vulnerability in flowise (npm), affecting versions < 2.1.4. It is fixed in 2.1.4.
- Which versions of flowise are affected by GHSA-5CPH-WVM9-45GJ? flowise (npm) versions < 2.1.4 is affected.
- Is there a fix for GHSA-5CPH-WVM9-45GJ? Yes. GHSA-5CPH-WVM9-45GJ is fixed in 2.1.4. Upgrade to this version or later.
- Is GHSA-5CPH-WVM9-45GJ exploitable, and should I be worried? Whether GHSA-5CPH-WVM9-45GJ is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-5CPH-WVM9-45GJ is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-5CPH-WVM9-45GJ? Upgrade
flowiseto 2.1.4 or later.