CVE-2025-59528

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2025-09-15. NVD baseline CVSS 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekWeaponized

Also known asEUVD-2025-29246 (ENISA EUVD) · GHSA-3gcm-f6qx-ff7p (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 86%
  • Public exploit code is available (Metasploit, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 86%CVSS: 10.0Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is available — apply it.

Flowise is a drag & drop user interface to build a customized large language model flow. In version 3.0.5, Flowise is vulnerable to remote code execution. The CustomMCP node allows users to input configuration settings for connecting to an external MCP server. This node parses the user-provided mcpServerConfig string to build the MCP server configuration. However, during this process, it executes JavaScript code without any security validation. Specifically, inside the convertToValidJSONString function, user input is directly passed to the Function() constructor, which evaluates and executes the input as JavaScript code. Since this runs with full Node.js runtime privileges, it can access dangerous modules such as child_process and fs. This issue has been patched in version 3.0.6.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
95
EG Risk 95/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation86% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
86%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
86% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 22, 2025

Last Modified

October 18, 2026

Advisory Details (8)

Auto-updated Nov 1, 2026
Patch available. Sources: github, github_release.
GitHub advisoryMentions a patch (unverified)

RCE in FlowiseAI/Flowise · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-3gcm-f6qx-ff7p
GitHub release Patch Available

flowise@3.0.6

Patch available: FlowiseAI/Flowise flowise@3.0.6

https://github.com/FlowiseAI/Flowise/releases/tag/flowise%403.0.6
Web page

Flowise/packages/server/src/services/nodes/index.ts at 5930f1119c655bcf8d2200ae827a1f5b9fec81d0 · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/blob/5930f1119c655bcf8d2200ae827a1f5b9fec81d0/packages/server/src/services/nodes/index.ts#L91-L94
Web page

Flowise/packages/server/src/routes/node-load-methods/index.ts at 5930f1119c655bcf8d2200ae827a1f5b9fec81d0 · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/blob/5930f1119c655bcf8d2200ae827a1f5b9fec81d0/packages/server/src/routes/node-load-methods/index.ts#L5
Web page

Flowise/packages/server/src/controllers/nodes/index.ts at 5930f1119c655bcf8d2200ae827a1f5b9fec81d0 · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/blob/5930f1119c655bcf8d2200ae827a1f5b9fec81d0/packages/server/src/controllers/nodes/index.ts#L57-L78
Web page

Flowise/packages/components/nodes/tools/MCP/CustomMCP/CustomMCP.ts at 5930f1119c655bcf8d2200ae827a1f5b9fec81d0 · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/blob/5930f1119c655bcf8d2200ae827a1f5b9fec81d0/packages/components/nodes/tools/MCP/CustomMCP/CustomMCP.ts#L262-L270
Web page

Flowise/packages/components/nodes/tools/MCP/CustomMCP/CustomMCP.ts at 5930f1119c655bcf8d2200ae827a1f5b9fec81d0 · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/blob/5930f1119c655bcf8d2200ae827a1f5b9fec81d0/packages/components/nodes/tools/MCP/CustomMCP/CustomMCP.ts#L220
Web page

Flowise/packages/components/nodes/tools/MCP/CustomMCP/CustomMCP.ts at 5930f1119c655bcf8d2200ae827a1f5b9fec81d0 · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/blob/5930f1119c655bcf8d2200ae827a1f5b9fec81d0/packages/components/nodes/tools/MCP/CustomMCP/CustomMCP.ts#L132

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmflowise @ 3.0.6 (fixes = 3.0.5)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
flowise3.0.5
  • 3.0.5 up to 3.0.6: fixed in 3.0.6
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 91 of 103 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 9 repeat rows among the latest 100 are merged into the row they repeat. The 12 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 05:52 UTCEG score recompute
  2. 2026-11-02 05:52 UTCGHSA enrichmentGHSA-3gcm-f6qx-ff7p · GitHub severity CRITICAL · GitHub CVSS 10.0
  3. 2026-11-01 08:03 UTCGHSA enrichmentGHSA-3gcm-f6qx-ff7p · GitHub severity CRITICAL · GitHub CVSS 10.0
  4. 2026-11-01 08:03 UTCEG score recompute
  5. 2026-11-01 07:09 UTCEG score recompute
  6. 2026-10-31 16:31 UTCEPSS rescoreEPSS 86% · 99th percentile
  7. 2026-10-31 08:25 UTCEG score recompute
  8. 2026-10-30 16:33 UTCEPSS rescoreEPSS 86% · 99th percentile
  9. 2026-10-30 09:42 UTCEG score recompute
  10. 2026-10-29 11:00 UTCEG score recompute
  11. 2026-10-28 16:30 UTCEPSS rescoreEPSS 86% · 99th percentile
  12. 2026-10-28 12:05 UTCEG score recompute
  13. 2026-10-27 16:30 UTCEPSS rescoreEPSS 86% · 99th percentile
  14. 2026-10-27 13:22 UTCEG score recompute
  15. 2026-10-26 14:13 UTCEG score recompute
  16. 2026-10-25 16:31 UTCEPSS rescoreEPSS 86% · 99th percentile
  17. 2026-10-25 15:01 UTCEG score recompute
  18. 2026-10-24 16:31 UTCEPSS rescoreEPSS 86% · 99th percentile
  19. 2026-10-23 17:35 UTCEG score recompute
  20. 2026-10-22 18:53 UTCEG score recompute
  21. 2026-10-21 20:09 UTCEG score recompute
  22. 2026-10-21 16:31 UTCEPSS rescoreEPSS 86% · 99th percentile
  23. 2026-10-20 21:27 UTCEG score recompute
  24. 2026-10-19 22:43 UTCEG score recompute
  25. 2026-10-19 16:31 UTCEPSS rescoreEPSS 86% · 99th percentile
Show 66 more
  1. 2026-10-18 16:43 UTCEG score recompute
  2. 2026-10-18 16:31 UTCEPSS rescoreEPSS 86% · 99th percentile
  3. 2026-10-18 05:23 UTCEG score recompute
  4. 2026-10-17 18:01 UTCEG score recompute
  5. 2026-10-16 19:18 UTCEG score recompute
  6. 2026-10-15 16:46 UTCEG score recompute
  7. 2026-10-14 16:31 UTCEPSS rescoreEPSS 86% · 99th percentile
  8. 2026-10-14 10:48 UTCEG score recompute
  9. 2026-10-12 16:53 UTCEG score recompute
  10. 2026-10-11 20:27 UTCEG score recompute
  11. 2026-10-11 18:39 UTCEG score recompute
  12. 2026-10-11 15:14 UTCEG score recompute
  13. 2026-10-09 20:06 UTCEPSS rescoreEPSS 86% · 99th percentile
  14. 2026-10-06 15:17 UTCEPSS rescoreEPSS 86% · 99th percentile
  15. 2026-10-02 04:40 UTCOSV refresh
  16. 2026-10-01 19:49 UTCEPSS rescoreEPSS 86% · 99th percentile
  17. 2026-09-24 14:02 UTCEPSS rescoreEPSS 86% · 99th percentile
  18. 2026-09-18 19:27 UTCEPSS rescoreEPSS 86% · 99th percentile
  19. 2026-09-16 14:07 UTCEPSS rescoreEPSS 86% · 99th percentile
  20. 2026-09-12 23:06 UTCOSV refresh
  21. 2026-09-12 15:00 UTCEPSS rescoreEPSS 86% · 99th percentile
  22. 2026-09-10 09:34 UTCEPSS rescoreEPSS 87% · 99th percentile
  23. 2026-09-06 13:47 UTCEPSS rescoreEPSS 87% · 99th percentile
  24. 2026-09-05 15:28 UTCEPSS rescoreEPSS 87% · 99th percentile
  25. 2026-09-04 05:06 UTCEPSS rescoreEPSS 87% · 99th percentile
  26. 2026-08-30 19:16 UTCEPSS rescoreEPSS 87% · 99th percentile
  27. 2026-08-30 01:21 UTCEPSS rescoreEPSS 87% · 99th percentile
  28. 2026-08-28 21:40 UTCEPSS rescoreEPSS 87% · 99th percentile
  29. 2026-08-26 14:45 UTCEPSS rescoreEPSS 87% · 99th percentile
  30. 2026-08-25 13:48 UTCEPSS rescoreEPSS 87% · 99th percentile
  31. 2026-08-25 03:26 UTCOSV refresh
  32. 2026-08-24 14:16 UTCEPSS rescoreEPSS 87% · 99th percentile
  33. 2026-08-24 09:22 UTCEPSS rescoreEPSS 87% · 99th percentile
  34. 2026-08-23 00:18 UTCEPSS rescoreEPSS 91% · 99th percentile
  35. 2026-08-21 23:48 UTCEPSS rescoreEPSS 91% · 99th percentile
  36. 2026-08-20 22:54 UTCEPSS rescoreEPSS 91% · 99th percentile
  37. 2026-08-19 17:03 UTCEPSS rescoreEPSS 91% · 99th percentile
  38. 2026-08-18 13:47 UTCEPSS rescoreEPSS 90% · 99th percentile
  39. 2026-08-16 02:13 UTCEPSS rescoreEPSS 90% · 99th percentile
  40. 2026-08-11 13:42 UTCEPSS rescoreEPSS 90% · 99th percentile
  41. 2026-08-08 20:49 UTCOSV refresh
  42. 2026-08-08 16:36 UTCEPSS rescoreEPSS 90% · 99th percentile
  43. 2026-08-04 15:09 UTCEPSS rescoreEPSS 90% · 99th percentile
  44. 2026-08-03 10:35 UTCEPSS rescoreEPSS 90% · 99th percentile
  45. 2026-08-01 04:15 UTCEPSS rescoreEPSS 90% · 99th percentile
  46. 2026-07-28 15:35 UTCEPSS rescoreEPSS 90% · 99th percentile
  47. 2026-07-24 14:17 UTCEPSS rescoreEPSS 90% · 99th percentile
  48. 2026-07-23 19:41 UTCOSV refresh
  49. 2026-07-23 03:00 UTCEG score recompute
  50. 2026-07-22 14:07 UTCEPSS rescoreEPSS 90% · 99th percentile
  51. 2026-07-15 16:57 UTCEPSS rescoreEPSS 90% · 99th percentile
  52. 2026-07-06 13:41 UTCOSV refresh
  53. 2026-07-02 17:01 UTCEPSS rescoreEPSS 90% · 99th percentile
  54. 2026-06-25 13:49 UTCEPSS rescoreEPSS 90% · 99th percentile
  55. 2026-06-24 14:04 UTCEPSS rescoreEPSS 90% · 99th percentile
  56. 2026-06-23 21:32 UTCEPSS rescoreEPSS 90% · 99th percentile
  57. 2026-06-18 17:52 UTCEPSS rescoreEPSS 90% · 99th percentile
  58. 2026-06-18 02:05 UTCOSV refresh
  59. 2026-06-16 17:52 UTCEPSS rescoreEPSS 90% · 99th percentile
  60. 2026-06-15 17:48 UTCEPSS rescoreEPSS 90% · 99th percentile
  61. 2026-06-14 23:17 UTCEPSS rescoreEPSS 85% · 99th percentile
  62. 2026-06-13 23:00 UTCEPSS rescoreEPSS 85% · 99th percentile
  63. 2026-06-12 23:11 UTCEPSS rescoreEPSS 85% · 99th percentile
  64. 2026-06-10 22:18 UTCEPSS rescoreEPSS 85% · 99th percentile
  65. 2026-06-10 13:22 UTCEPSS rescoreEPSS 85% · 99th percentile
  66. 2026-06-08 14:16 UTCEPSS rescoreEPSS 85% · 99th percentile

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Metasploitexploit/multi/http/flowise_js_rce✓ verified
    Published Nov 21, 2025

    Flowise JS Injection RCE

    Open source ↗
  • Nucleihttp/cves/2025/CVE-2025-59528.yaml
    Published Apr 6, 2026

    Flowise - Remote Code Execution

    Open source ↗
  • Exploit-DBEDB-52440
    Published Oct 31, 2025

    Flowise 3.0.4 - Remote Code Execution (RCE)

    Open source ↗

Frequently asked(5)

What is CVE-2025-59528?
CVE-2025-59528 is a critical-severity vulnerability; its CVE record was published on September 22, 2025. Flowise is a drag & drop user interface to build a customized large language model flow. In version 3.0.5, Flowise is vulnerable to remote code execution. The CustomMCP node allows users to input configuration settings for connecting to an external MCP server. This node parses the user-provided…
When was the CVE record for CVE-2025-59528 published?
The CVE record for CVE-2025-59528 was published on September 22, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 18, 2026; the record at its source may have been updated since.
Is CVE-2025-59528 actively exploited?
CVE-2025-59528 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it, and CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 86% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-59528?
CVE-2025-59528 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2025-59528?
A fix for CVE-2025-59528 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-59528

Explore →

Is Your Infrastructure Affected by CVE-2025-59528?

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