CVE-2026-69255

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 53% 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 weekElevated
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: Elevated riskExposed: 0

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

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, the CSVAgent in packages/components/nodes/agents/CSVAgent/CSVAgent.ts extracted attacker-controlled CSV data with file.split(',').pop() and interpolated it directly into executable Python as base64_string = "${base64String}" before calling Pyodide. The validatePythonCodeForDataFrame() denylist only checked later LLM-generated code and did not validate this initial code block. An authenticated attacker could inject a closing quote followed by Python code, use Pyodide's js bridge to load Node.js child_process, and execute arbitrary operating system commands as root in the Flowise container. This issue is fixed in version 3.1.3.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
56(Track*)
EG Risk 56/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%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

August 4, 2026

Last Modified

September 14, 2026

Advisory Details (4)

Auto-updated Sep 7, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

CSV Agent Remote Code Execution via Pyodide Code Injection — Root Shell Verified · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-vmv7-4m6c-3cg5
github_release Patch Available

[email protected]

Patch available: FlowiseAI/Flowise [email protected]

https://github.com/FlowiseAI/Flowise/releases/tag/flowise%403.1.3
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-69255(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 11× 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.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-69255?
CVE-2026-69255 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, the CSVAgent in packages/components/nodes/agents/CSVAgent/CSVAgent.ts extracted attacker-controlled CSV data with file.split(',').pop() and interpolated it directly into executable Python as…
When was CVE-2026-69255 disclosed?
CVE-2026-69255 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-69255 actively exploited?
CVE-2026-69255 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 52.6% of all scored CVEs.
What is the CVSS score of CVE-2026-69255?
CVE-2026-69255 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-69255?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69255, 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-69255

Explore →

Is Your Infrastructure Affected by CVE-2026-69255?

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

Start Free Scan →Browse All CVEs