CVE-2026-69253

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 51% 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, nvd
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

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

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.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

August 4, 2026

Last Modified

September 14, 2026

Advisory Details (4)

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

[email protected]

Patch available: FlowiseAI/Flowise [email protected]

https://github.com/FlowiseAI/Flowise/releases/tag/[email protected]
github_commit Patch Available

commit 3f257bdc8196 (FlowiseAI/Flowise)

Patch available: FlowiseAI/Flowise [email protected] (contains commit 3f257bdc8196)

https://github.com/FlowiseAI/Flowise/commit/3f257bdc8196082a178da7134a075824401b13b9
github_pr Patch Available

fix: FLOWISE-400, 543, 551

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

https://github.com/FlowiseAI/Flowise/pull/6417
github Patch Available

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.

Affected Packages

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFixed inDependents
flowise—3.1.3—
flowise-components—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 / 51× 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-09-19 08:02 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 05:26 UTCEG score recompute
  4. 2026-09-17 01:12 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:16 UTCEG score recompute
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 09:26 UTCEG score recompute
  9. 2026-09-14 20:14 UTCEG score recompute▼ 0.20
  10. 2026-09-14 20:13 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
  11. 2026-09-13 17:02 UTCEG score recompute
  12. 2026-09-12 16:31 UTCEG score recompute
  13. 2026-09-11 19:19 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 14:52 UTCEG score recompute
  16. 2026-09-11 09:37 UTCEPSS rescore
  17. 2026-09-10 12:49 UTCEG score recompute
  18. 2026-09-09 06:37 UTCEG score recompute
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-06 14:37 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:15 UTCEG score recompute
  25. 2026-09-04 10:10 UTCEG score recompute
Show 60 more
  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-03 07:31 UTCEG score recompute
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 20:50 UTCEG score recompute
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-09-01 07:19 UTCEG score recompute
  7. 2026-09-01 04:40 UTCEPSS rescore
  8. 2026-08-30 22:02 UTCEG score recompute
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 01:49 UTCEG score recompute
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-29 21:48 UTCEG score recompute
  13. 2026-08-28 21:42 UTCEPSS rescore
  14. 2026-08-27 19:57 UTCEG score recompute
  15. 2026-08-26 19:10 UTCEG score recompute
  16. 2026-08-26 14:47 UTCEPSS rescore
  17. 2026-08-25 13:51 UTCEG score recompute
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-24 17:43 UTCEG score recompute
  20. 2026-08-24 12:43 UTCEG score recompute
  21. 2026-08-23 00:34 UTCEG score recompute
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-22 00:21 UTCEG score recompute
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-21 00:12 UTCEG score recompute
  26. 2026-08-20 22:56 UTCEPSS rescore
  27. 2026-08-19 19:59 UTCEG score recompute
  28. 2026-08-19 17:04 UTCEPSS rescore
  29. 2026-08-18 15:48 UTCEG score recompute
  30. 2026-08-18 13:49 UTCEPSS rescore
  31. 2026-08-18 13:49 UTCEPSS rescore
  32. 2026-08-17 19:35 UTCEG score recompute
  33. 2026-08-17 13:47 UTCEPSS rescore
  34. 2026-08-16 17:40 UTCEG score recompute
  35. 2026-08-16 14:56 UTCEPSS rescore
  36. 2026-08-16 14:56 UTCEPSS rescore
  37. 2026-08-16 05:31 UTCEG score recompute
  38. 2026-08-16 02:15 UTCEPSS rescore
  39. 2026-08-15 05:25 UTCEG score recompute
  40. 2026-08-15 01:30 UTCEPSS rescore
  41. 2026-08-14 01:17 UTCEG score recompute
  42. 2026-08-13 22:00 UTCEPSS rescore
  43. 2026-08-12 17:08 UTCEG score recompute
  44. 2026-08-12 13:51 UTCEPSS rescore
  45. 2026-08-11 17:03 UTCEG score recompute
  46. 2026-08-11 01:00 UTCEG score recompute
  47. 2026-08-11 00:00 UTCEPSS rescore
  48. 2026-08-09 16:53 UTCEG score recompute
  49. 2026-08-09 13:47 UTCEPSS rescore
  50. 2026-08-07 16:43 UTCEG score recompute
  51. 2026-08-06 16:38 UTCEG score recompute
  52. 2026-08-06 13:47 UTCEPSS rescore
  53. 2026-08-05 20:34 UTCEG score recompute
  54. 2026-08-05 19:17 UTCEPSS rescore
  55. 2026-08-05 19:17 UTCEPSS rescore
  56. 2026-08-05 16:32 UTCEG score recompute
  57. 2026-08-05 15:30 UTCEG score recompute
  58. 2026-08-04 16:33 UTCEG score recompute
  59. 2026-08-04 15:37 UTCEG score recompute
  60. 2026-08-04 15:37 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-69253?
CVE-2026-69253 is a high vulnerability 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 CVE-2026-69253 disclosed?
CVE-2026-69253 was first published in the National Vulnerability Database 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-69253 actively exploited?
CVE-2026-69253 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 51.3% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69253, 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

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.

Start Free Scan →Browse All CVEs