CVE-2026-58057

MEDIUMPre-NVD 5.05.0—
EchelonGraph scoreHIGH confidence

Score 5.0 from GitHub Security Advisory (severity: LOW) published 2026-06-28. a secondary CVSS source baseline 5.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
5.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
5.0
EG Score
5.0(high)
EPSS
15.1%
KEV
Not listed

Published

June 28, 2026

Last Modified

July 6, 2026

Advisory Details (3)

Auto-updated Jun 28, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr.
generic🟡 PoC Available

Flowise - Custom MCP Environment Variable Denylist Bypass via Case Sensitivity | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-custom-mcp-environment-variable-denylist-bypass-via-case-sensitivity
generic

exploitarium/flowise-mcp-env-case-bypass-poc at main · bikini/exploitarium · GitHub

https://github.com/bikini/exploitarium/tree/main/flowise-mcp-env-case-bypass-poc
github_pr Patch Available

Fix Flowise 552

Patch available: FlowiseAI/Flowise [email protected] (PR #6471 merged 2026-06-03)

https://github.com/FlowiseAI/Flowise/pull/6471

Vendor Advisories for CVE-2026-58057(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 24× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:54 UTCEG score recompute
  2. 2026-07-06 16:54 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 17:55 UTCEG score recompute
  8. 2026-07-05 17:55 UTCGHSA enrichment
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 18:58 UTCEG score recompute
  12. 2026-07-04 18:58 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-03 20:00 UTCEG score recompute
  16. 2026-07-03 20:00 UTCGHSA enrichment
  17. 2026-07-02 21:02 UTCEG score recompute
  18. 2026-07-02 21:02 UTCGHSA enrichment
  19. 2026-07-01 22:05 UTCEG score recompute
  20. 2026-07-01 22:05 UTCGHSA enrichment
  21. 2026-07-01 15:07 UTCEPSS rescore
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 23:04 UTCEG score recompute
  24. 2026-06-30 23:03 UTCGHSA enrichment
  25. 2026-06-30 00:06 UTCEG score recompute
Show 7 more
  1. 2026-06-30 00:05 UTCGHSA enrichment
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-29 01:08 UTCEG score recompute
  4. 2026-06-29 01:08 UTCGHSA enrichment
  5. 2026-06-28 14:07 UTCEPSS rescore
  6. 2026-06-28 02:10 UTCEG score recompute
  7. 2026-06-28 02:09 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-58057?
CVE-2026-58057 is a medium vulnerability published on June 28, 2026. 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 'nodeoptions' bypasses the NODEOPTIONS denylist entry. An authenticated user who can configure a Custom…
When was CVE-2026-58057 disclosed?
CVE-2026-58057 was first published in the National Vulnerability Database on June 28, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58057 actively exploited?
CVE-2026-58057 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58057?
CVE-2026-58057 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2026-58057?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58057, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-58057

Explore →

Is Your Infrastructure Affected by CVE-2026-58057?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs