CVE-2026-69253

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.7% (51st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-52739 (ENISA EUVD) · GHSA-wg86-r78f-74mp (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. Prior to version 3.1.3, several custom-tool components — AgentAsTool, ChatflowTool, and ExecuteFlow — ran code in the in-process  vm2  sandbox. To build that code, they inserted a user-controlled  baseURL  value straight into the JavaScript source, for example  const url = "${baseURL}/..."; . The only check on  baseURL  was  isValidURL , but a valid-looking URL can still contain characters that break out of a code string. An authenticated user could craft a  baseURL  that passed this check, closed the surrounding string, and injected their own JavaScript into the sandboxed script (code injection, CWE-94). The  vm2  sandbox runs in the same Node.js process as Flowise and exposes risky dependencies. As a result, the injected code could escape the sandbox and run arbitrary code on the Flowise server as the Flowise process user. Exploitation only requires an authenticated session. The issue is fixed in version 3.1.3, which passes the URL to the sandbox as data instead of inserting it into code and adds stricter URL validation.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.7%
EPSS %ILE
51st
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

August 4, 2026

Last Modified

October 23, 2026

Advisory Details (4)

Auto-updated Aug 4, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

flowise@3.1.3

Patch available: FlowiseAI/Flowise flowise@3.1.3

https://github.com/FlowiseAI/Flowise/releases/tag/flowise@3.1.3
GitHub commit Patch Available

commit 3f257bdc8196 (FlowiseAI/Flowise)

Patch available: FlowiseAI/Flowise flowise@3.1.3 (contains commit 3f257bdc8196)

https://github.com/FlowiseAI/Flowise/commit/3f257bdc8196082a178da7134a075824401b13b9
GitHub pull request Patch Available

fix: FLOWISE-400, 543, 551

Patch available: FlowiseAI/Flowise flowise@3.1.3 (PR #6417 merged 2026-06-16)

https://github.com/FlowiseAI/Flowise/pull/6417
GitHub advisoryMentions a patch (unverified)

Flowise Sandbox Escape to RCE · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-wg86-r78f-74mp

Vendor Advisories for CVE-2026-69253(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmflowise @ 3.1.3 (fixes <= 3.1.2)—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

(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 10× in last 7d / 46× 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 100 of 151 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. None are among the latest 100 rows. The 51 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-69253?
CVE-2026-69253 is a high-severity vulnerability; its CVE record was published on August 4, 2026. Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. Prior to version 3.1.3, several custom-tool components — AgentAsTool, ChatflowTool, and ExecuteFlow — ran code in the in-process vm2 sandbox. To build that code, they inserted a user-controlled…
When was the CVE record for CVE-2026-69253 published?
The CVE record for CVE-2026-69253 was published on August 4, 2026. 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 23, 2026; the record at its source may have been updated since.
Is CVE-2026-69253 actively exploited?
CVE-2026-69253 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-69253?
CVE-2026-69253 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-69253?
A fix for CVE-2026-69253 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69253 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-69253

Explore →

Is Your Infrastructure Affected by CVE-2026-69253?

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

Book a Demo →Browse All CVEs