Unauthenticated code execution via unrestricted configuration overrides
Published Jun 20, 2026 · Updated Jun 20, 2026
Code injection in Flowise before 2.1.4 allows remote attackers to execute code via overrideConfig in web embeds or the Prediction API. The execution path accepts unrestricted configuration keys, applies them to the running Chainflow, and relies on vm2 to contain attacker-controlled behavior. The feature is enabled by default and requires no authentication; abuse is self-targeted but can escape the sandbox, crash the server, make server-side requests, alter prompts, and exfiltrate server data.
Summary
What happened
Code injection in Flowise before 2.1.4 allows remote attackers to execute code via overrideConfig in web embeds or the Prediction API. The execution path accepts unrestricted configuration keys, applies them to the running Chainflow, and relies on vm2 to contain attacker-controlled behavior. The feature is enabled by default and requires no authentication; abuse is self-targeted but can escape the sandbox, crash the server, make server-side requests, alter prompts, and exfiltrate server data.
The record
- CVE
- CVE-2024-58351
- Published
- Jun 20, 2026
- Updated
- Jun 20, 2026
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- CWE-94, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 20, 2026CVE publishedPublication date reported by the CVE source.
- Jun 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.1.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo