CVE-2026-69264

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.1% (64th 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
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 9.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Prior to 3.1.3, Flowise CSVAgent interpolates an attacker-controlled segment of the csvFile data URI directly into a Python source-code template that is then executed by Pyodide. Because Pyodide is loaded with the default js bridge to globalThis, which on Node.js exposes eval and dynamic import, the attacker can break out of the Python string literal, hand a JavaScript string to js.eval, dynamically import Node built-in modules such as fs and child_process, and execute arbitrary file I/O or OS commands as the Flowise process. The two validator paths around this code, validatePythonCodeForDataFrame and validateCustomReadCSVFunction, are never applied to the bootstrap template. A workspace user with chatflows:create or agentflows/chatflows update permission can plant a CSV Agent node with a crafted csvFile; once the chatflow is exposed via POST /api/v1/prediction/:id, any unauthenticated request triggers host remote code execution. This issue is fixed in version 3.1.3.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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
Severity98% × 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
1.1%
EPSS %ILE
64th
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 28, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Rce viaCSVAgent csvFile data URI base64 segment is interpolated into Python source without validation, · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-4j8x-x6v7-w9rq
github_release Patch Available

[email protected]

Patch available: FlowiseAI/Flowise [email protected]

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

Fix Flowise 606

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

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

commit f4e2794f6a57 (FlowiseAI/Flowise)

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

https://github.com/FlowiseAI/Flowise/commit/f4e2794f6a576b94578f2fdafbf49c2fb304626c

Vendor Advisories for CVE-2026-69264(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(2)

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

Data Freshness Timeline

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-69264?
CVE-2026-69264 is a critical vulnerability published on August 4, 2026. Prior to 3.1.3, Flowise CSVAgent interpolates an attacker-controlled segment of the csvFile data URI directly into a Python source-code template that is then executed by Pyodide. Because Pyodide is loaded with the default js bridge to globalThis, which on Node.js exposes eval and dynamic import,…
When was CVE-2026-69264 disclosed?
CVE-2026-69264 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-69264 actively exploited?
CVE-2026-69264 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (64th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69264?
CVE-2026-69264 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-69264?
A fix for CVE-2026-69264 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69264 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-69264

Explore →

Is Your Infrastructure Affected by CVE-2026-69264?

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

Book a Demo →Browse All CVEs