CVE•Published 2026-06-28•Modified 2026-07-06•0 articles on news•5 live references•NVD data

CVE-2026-58057Flowiseai · Flowise

Vulnerability data via NVD (ingested)

CVSS v3.1

5.0

MEDIUM

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

EPSS percentile

Exploit Prediction Scoring System · top 85% of all CVEs

Weaknesses (CWE)

CWE-178Improper Handling of Case Sensitivity

Description

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.

Timeline

Published 2026-06-28

Modified 2026-07-06

External references

NVD MITRE Exploit-DB trickest/cve VulnCheck

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).

Shodan · vuln tag556 hosts

vuln:CVE-2026-58057

Hosts Shodan has explicitly fingerprinted as vulnerable.

Shodan · product

product:"Flowiseai Flowise"

All exposed Flowiseai Flowise instances — cross-reference with the CVE's affected-version range.

Shodan · banner/body mention

http.html:"Flowise"

HTTP body or banner mentions "Flowise" — catches deploys Shodan didn't identify as a product.

More intel sources (5)

Shodan report

vuln:CVE-2026-58057