CVE-2026-58057Public exploitNetwork attack vector

Authenticated code execution via case-insensitive environment names

Published Jun 28, 2026 · Updated Jun 28, 2026

Improper case handling in Flowise before 3.1.3 allows remote authenticated users to execute code through Custom MCP stdio on Windows. The environment validator compares supplied names to a case-sensitive denylist, so node_options evades the NODE_OPTIONS entry but is honored by Windows and passed to a spawned process. Exploitation requires access to configure a Custom MCP stdio node and a command that starts Node.js, where --require loads attacker-selected JavaScript in the server context.

CVSS severity2.3
Low
EPSS probability1.56%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper case handling in Flowise before 3.1.3 allows remote authenticated users to execute code through Custom MCP stdio on Windows. The environment validator compares supplied names to a case-sensitive denylist, so node_options evades the NODE_OPTIONS entry but is honored by Windows and passed to a spawned process. Exploitation requires access to configure a Custom MCP stdio node and a command that starts Node.js, where --require loads attacker-selected JavaScript in the server context.

The record

CVE
CVE-2026-58057
Published
Jun 28, 2026
Updated
Jun 28, 2026
Vendor
FlowiseAI
Product
Flowise
Classifications
CWE-178, T1059.007
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 28, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 28, 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.

  1. Affected versionversion=0 <3.1.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

FlowiseAI · Flowiseversion=0 <3.1.3

Published CVSS scores

5.0VulnCheckCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
2.3VulnCheckCVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-178Improper Handling of Case Sensitivity
T1059.007JavaScript/JScript

Public exploit references

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