CVE-2026-69254

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.7% (51st percentile of EPSS-scored CVEs). 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, nvd
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, executeJavaScriptCode() accepted caller-provided nodeVMOptions and merged them over the default NodeVM security settings in packages/components/src/utils.ts. An authenticated attacker reaching packages/server/src/routes/node-custom-functions/index.ts could run a custom function that imported flowise-components/dist/src/utils.js, called executeJavaScriptCode() again with nodeVMOptions.require.builtin set to allow all built-in modules, and then required child_process to execute arbitrary system commands as root on the Flowise server. This issue is fixed in version 3.1.3.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/100CISA SSVC

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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
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
0.7%
EPSS %ILE
51st
KEV
Not listed

CISA SSVCTrack 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 no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 4, 2026

Last Modified

September 14, 2026

Advisory Details (4)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

RCE via NodeVM Sandbox Escape in executeJavaScriptCode() nodeVMOptions Override · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-3769-jgqc-cxm7
github_pr Patch Available

Fix FLOWISE 429 executeJavaScriptCode

Patch available: FlowiseAI/Flowise [email protected] (PR #6306 merged 2026-04-30)

https://github.com/FlowiseAI/Flowise/pull/6306
github_commit Patch Available

commit 3086cb7e323b (FlowiseAI/Flowise)

Patch available: FlowiseAI/Flowise [email protected] (contains commit 3086cb7e323b)

https://github.com/FlowiseAI/Flowise/commit/3086cb7e323bb96c5a581d3232ef975b0d92183d

Vendor Advisories for CVE-2026-69254(1)

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

Affected Packages

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFix by version rangeDependents
flowise—
  • every version up to 3.1.3: fixed in 3.1.3
—
flowise-components—
  • every version up to 3.1.3: fixed in 3.1.3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 48× 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.

Showing the most recent 100 of 112 total refreshes for this CVE.

  1. 2026-10-04 23:40 UTCEG score recompute
  2. 2026-10-04 23:22 UTCEPSS rescore
  3. 2026-10-04 06:12 UTCEG score recompute
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-03 01:58 UTCEG score recompute
  6. 2026-10-02 17:56 UTCEPSS rescore
  7. 2026-10-02 10:11 UTCEG score recompute
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-10-01 02:27 UTCEG score recompute
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 06:26 UTCEG score recompute
  12. 2026-09-28 13:52 UTCEPSS rescore
  13. 2026-09-27 18:03 UTCEG score recompute
  14. 2026-09-27 13:48 UTCEPSS rescore
  15. 2026-09-26 15:59 UTCEPSS rescore
  16. 2026-09-25 04:42 UTCEG score recompute
  17. 2026-09-24 02:15 UTCEG score recompute
  18. 2026-09-23 17:54 UTCEPSS rescore
  19. 2026-09-23 02:36 UTCEG score recompute
  20. 2026-09-22 03:25 UTCEG score recompute
  21. 2026-09-21 21:09 UTCEPSS rescore
  22. 2026-09-20 20:53 UTCEG score recompute
  23. 2026-09-20 20:16 UTCEPSS rescore
  24. 2026-09-19 17:45 UTCEG score recompute
  25. 2026-09-19 03:36 UTCEG score recompute
Show 75 more
  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 03:40 UTCEG score recompute
  3. 2026-09-17 01:12 UTCEG score recompute
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 07:37 UTCEG score recompute
  7. 2026-09-14 20:01 UTCEG score recompute▼ 0.60
  8. 2026-09-14 19:59 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
  9. 2026-09-13 20:01 UTCEG score recompute
  10. 2026-09-12 17:46 UTCEG score recompute
  11. 2026-09-11 19:19 UTCEG score recompute
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-11 14:52 UTCEG score recompute
  14. 2026-09-11 09:37 UTCEPSS rescore
  15. 2026-09-10 12:49 UTCEG score recompute
  16. 2026-09-09 06:37 UTCEG score recompute
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-07 18:35 UTCEG score recompute
  19. 2026-09-07 16:01 UTCEPSS rescore
  20. 2026-09-06 16:32 UTCEG score recompute
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-05 18:33 UTCEG score recompute
  23. 2026-09-05 15:31 UTCEPSS rescore
  24. 2026-09-04 14:31 UTCEG score recompute
  25. 2026-09-04 10:09 UTCEG score recompute
  26. 2026-09-04 05:07 UTCEPSS rescore
  27. 2026-09-03 07:31 UTCEG score recompute
  28. 2026-09-02 14:12 UTCEPSS rescore
  29. 2026-09-01 20:50 UTCEG score recompute
  30. 2026-09-01 13:54 UTCEPSS rescore
  31. 2026-09-01 07:18 UTCEG score recompute
  32. 2026-09-01 04:40 UTCEPSS rescore
  33. 2026-08-30 19:33 UTCEG score recompute
  34. 2026-08-30 19:17 UTCEPSS rescore
  35. 2026-08-30 02:08 UTCEG score recompute
  36. 2026-08-30 01:22 UTCEPSS rescore
  37. 2026-08-29 21:47 UTCEG score recompute
  38. 2026-08-28 21:42 UTCEPSS rescore
  39. 2026-08-27 19:57 UTCEG score recompute
  40. 2026-08-26 19:10 UTCEG score recompute
  41. 2026-08-26 14:47 UTCEPSS rescore
  42. 2026-08-25 15:35 UTCEG score recompute
  43. 2026-08-25 13:49 UTCEPSS rescore
  44. 2026-08-24 17:43 UTCEG score recompute
  45. 2026-08-24 11:59 UTCEG score recompute
  46. 2026-08-23 01:11 UTCEG score recompute
  47. 2026-08-23 00:19 UTCEPSS rescore
  48. 2026-08-22 03:29 UTCEG score recompute
  49. 2026-08-21 23:49 UTCEPSS rescore
  50. 2026-08-21 01:29 UTCEG score recompute
  51. 2026-08-20 22:56 UTCEPSS rescore
  52. 2026-08-19 18:56 UTCEG score recompute
  53. 2026-08-19 17:04 UTCEPSS rescore
  54. 2026-08-18 15:48 UTCEG score recompute
  55. 2026-08-18 13:49 UTCEPSS rescore
  56. 2026-08-18 13:49 UTCEPSS rescore
  57. 2026-08-17 17:07 UTCEG score recompute
  58. 2026-08-17 13:47 UTCEPSS rescore
  59. 2026-08-16 15:00 UTCEG score recompute
  60. 2026-08-16 14:56 UTCEPSS rescore
  61. 2026-08-16 14:56 UTCEPSS rescore
  62. 2026-08-16 06:20 UTCEG score recompute
  63. 2026-08-16 02:15 UTCEPSS rescore
  64. 2026-08-15 04:21 UTCEG score recompute
  65. 2026-08-15 01:30 UTCEPSS rescore
  66. 2026-08-14 02:19 UTCEG score recompute
  67. 2026-08-13 22:00 UTCEPSS rescore
  68. 2026-08-12 15:33 UTCEG score recompute
  69. 2026-08-12 13:51 UTCEPSS rescore
  70. 2026-08-11 17:53 UTCEG score recompute
  71. 2026-08-11 00:34 UTCEG score recompute
  72. 2026-08-11 00:00 UTCEPSS rescore
  73. 2026-08-09 17:47 UTCEG score recompute
  74. 2026-08-09 13:47 UTCEPSS rescore
  75. 2026-08-08 20:08 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-69254?
CVE-2026-69254 is a high vulnerability published on August 4, 2026. Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, executeJavaScriptCode() accepted caller-provided nodeVMOptions and merged them over the default NodeVM security settings in packages/components/src/utils.ts. An authenticated attacker reaching…
When was CVE-2026-69254 disclosed?
CVE-2026-69254 was first published on August 4, 2026, with the most recent update on September 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-69254 actively exploited?
CVE-2026-69254 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69254?
CVE-2026-69254 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-69254?
A fix for CVE-2026-69254 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69254 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69254

Explore →

Is Your Infrastructure Affected by CVE-2026-69254?

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