Flowise up to 3.1.2 on Windows Environment Variable case sensitivity
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 2.71+ |
Summary
A vulnerability marked as problematic has been reported in Flowise up to 3.1.2 on Windows. Impacted is an unknown function of the component Environment Variable Handler. Performing a manipulation results in case sensitivity. This vulnerability is identified as CVE-2026-58057. The attack can be initiated remotely. Additionally, an exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Flowise up to 3.1.2 on Windows. This affects an unknown code of the component Environment Variable Handler. The manipulation with an unknown input leads to a case sensitivity vulnerability. CWE is classifying the issue as CWE-178. The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Flowise before 3.1.3 validates Custom MCP stdio environment variables against a denylist using a case-sensitive comparison, so on Windows, where environment names are case-insensitive, supplying 'node_options' bypasses the NODE_OPTIONS denylist entry. An authenticated user who can configure a Custom MCP node can thereby inject NODE_OPTIONS --require and execute arbitrary code in the Flowise server context.
The weakness was released by ashdfrkl. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-58057 since 06/28/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. Technical details are unknown but a public exploit is available.
The exploit is shared for download at github.com. It is declared as proof-of-concept.
Upgrading to version 3.1.3 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.7
VulDB Base Score: 5.0
VulDB Temp Score: 4.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.0
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Case sensitivityCWE: CWE-178 / CWE-697
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Flowise 3.1.3
Patch: github.com
Timeline
06/28/2026 Advisory disclosed06/28/2026 CVE reserved
06/28/2026 VulDB entry created
06/28/2026 VulDB entry last update
Sources
Advisory: github.comResearcher: ashdfrkl
Status: Confirmed
CVE: CVE-2026-58057 (🔒)
GCVE (CVE): GCVE-0-2026-58057
GCVE (VulDB): GCVE-100-374511
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/28/2026 08:17Changes: 06/28/2026 08:17 (80)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.