Back to CVE records
Medium 5.0Published Jun 28, 2026

CVE-2026-58057Flowise 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 'nod…

Updated under an hour ago ()

Does this affect you?

It affects flowiseai flowise. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
5.0 MEDIUM (v3.1, NVD)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
Weakness (CWE)
CWE-178
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Not given
NVD analysis
Analyzed
Record last updated
Jul 6, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
flowiseai flowise
flowiseai:flowise
before 3.1.3
NVD

References

  • issue-tracking, patch
  • exploit, third-party-advisory
  • exploit, patch, third-party-advisory

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.
CVE-2026-58057: Flowise before 3.1.3 validates Custom MCP stdio environment variables against a denylist using a case-se | InfoSec Signals