CVE-2026-73601

CRITICALPre-NVD 9.09.0
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 54% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
9.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.0Exploit: None knownExposed: 0

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

Flowise versions before 3.1.3 contain a remote code execution vulnerability in the Custom MCP node when CUSTOM_MCP_PROTOCOL is set to stdio, allowing authenticated users to execute arbitrary commands by manipulating environment variables and command arguments. Attackers can abuse PYTHONWARNINGS and BROWSER environment variables with python3, or leverage the root working directory with node to bypass validation and execute system commands.

CVSS v3
9.0
EG Score
9.0(medium)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 14, 2026

Advisory Details (2)

Auto-updated Aug 13, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Flowise before 3.1.3 Remote Code Execution via Custom MCP | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-before-remote-code-execution-via-custom-mcp
github Patch Available🟡 PoC Available

Flowise RCE via Custom MCP Config Node · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-g98q-rm45-q9h8

Vendor Advisories for CVE-2026-73601(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 57× in last 7d / 59× 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-08-20 12:10 UTCGHSA enrichment
  2. 2026-08-20 07:45 UTCGHSA enrichment
  3. 2026-08-20 03:21 UTCGHSA enrichment
  4. 2026-08-19 22:56 UTCGHSA enrichment
  5. 2026-08-19 18:31 UTCEG score recompute
  6. 2026-08-19 18:31 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 13:25 UTCGHSA enrichment
  9. 2026-08-19 08:56 UTCGHSA enrichment
  10. 2026-08-19 04:31 UTCGHSA enrichment
  11. 2026-08-19 00:05 UTCGHSA enrichment
  12. 2026-08-18 19:37 UTCGHSA enrichment
  13. 2026-08-18 15:12 UTCEG score recompute
  14. 2026-08-18 15:12 UTCGHSA enrichment
  15. 2026-08-18 13:49 UTCEPSS rescore
  16. 2026-08-18 13:49 UTCEPSS rescore
  17. 2026-08-18 09:45 UTCGHSA enrichment
  18. 2026-08-18 05:21 UTCGHSA enrichment
  19. 2026-08-18 00:56 UTCGHSA enrichment
  20. 2026-08-17 20:32 UTCGHSA enrichment
  21. 2026-08-17 16:08 UTCEG score recompute
  22. 2026-08-17 16:08 UTCGHSA enrichment
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-17 11:44 UTCGHSA enrichment
  25. 2026-08-17 07:13 UTCGHSA enrichment
Show 34 more
  1. 2026-08-17 02:49 UTCGHSA enrichment
  2. 2026-08-16 22:25 UTCGHSA enrichment
  3. 2026-08-16 18:01 UTCEG score recompute
  4. 2026-08-16 18:01 UTCGHSA enrichment
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 13:37 UTCGHSA enrichment
  8. 2026-08-16 09:12 UTCGHSA enrichment
  9. 2026-08-16 04:49 UTCEG score recompute
  10. 2026-08-16 04:49 UTCGHSA enrichment
  11. 2026-08-16 02:15 UTCEPSS rescore
  12. 2026-08-16 00:25 UTCGHSA enrichment
  13. 2026-08-15 20:01 UTCGHSA enrichment
  14. 2026-08-15 15:37 UTCGHSA enrichment
  15. 2026-08-15 11:13 UTCGHSA enrichment
  16. 2026-08-15 06:49 UTCGHSA enrichment
  17. 2026-08-15 01:43 UTCEG score recompute
  18. 2026-08-15 01:43 UTCGHSA enrichment
  19. 2026-08-15 01:31 UTCEPSS rescore
  20. 2026-08-14 21:19 UTCEG score recompute
  21. 2026-08-14 21:19 UTCGHSA enrichment
  22. 2026-08-14 20:24 UTCEG score recompute
  23. 2026-08-14 20:24 UTCGHSA enrichment
  24. 2026-08-14 19:23 UTCGHSA enrichment
  25. 2026-08-14 14:59 UTCGHSA enrichment
  26. 2026-08-14 10:35 UTCGHSA enrichment
  27. 2026-08-14 06:11 UTCGHSA enrichment
  28. 2026-08-14 01:47 UTCGHSA enrichment
  29. 2026-08-13 21:23 UTCGHSA enrichment
  30. 2026-08-13 16:57 UTCGHSA enrichment
  31. 2026-08-13 12:33 UTCEG score recompute
  32. 2026-08-13 12:33 UTCGHSA enrichment
  33. 2026-08-13 11:42 UTCEG score recompute
  34. 2026-08-13 11:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-73601?
CVE-2026-73601 is a critical vulnerability published on August 13, 2026. Flowise versions before 3.1.3 contain a remote code execution vulnerability in the Custom MCP node when CUSTOMMCPPROTOCOL is set to stdio, allowing authenticated users to execute arbitrary commands by manipulating environment variables and command arguments. Attackers can abuse PYTHONWARNINGS and…
When was CVE-2026-73601 disclosed?
CVE-2026-73601 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73601 actively exploited?
CVE-2026-73601 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.6% of all scored CVEs.
What is the CVSS score of CVE-2026-73601?
CVE-2026-73601 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2026-73601?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73601, 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-73601

Explore →

Is Your Infrastructure Affected by CVE-2026-73601?

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