CVE-2026-70470

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.0% (62nd 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
Elevated

Also known asEUVD-2026-52811 (ENISA EUVD) · GHSA-52fh-8v99-63c2 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 9.8Exploit: No code on recordExposed 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, Flowise validatePythonCodeForDataFrame in packages/components/src/pythonCodeValidator.ts can be bypassed with Unicode homoglyph identifiers, allowing arbitrary Python execution inside Pyodide and full OS command execution on the Flowise host via Pyodide js module interop. The validator gates pyodide.runPythonAsync in packages/components/nodes/agents/CSVAgent/CSVAgent.ts and packages/components/nodes/agents/AirtableAgent/AirtableAgent.ts with an ASCII word-boundary blacklist. JavaScript regex word boundaries are ASCII-only, while Python 3 NFKC-normalizes identifiers at parse time, so homoglyph forms such as __cl𝐚ss__, __subcl𝐚sses__, __b𝐚se__, and __b𝐮iltins__ bypass the blacklist and are parsed as their ASCII equivalents. This issue is fixed in version 3.1.3.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
1.0%
EPSS %ILE
62nd
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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, Track* at medium and Attend at high mission impact.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, 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). 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 24, 2026

Advisory Details (4)

Auto-updated Nov 15, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Flowise: Pyodide validator Unicode homoglyph bypass leads to RCE · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-52fh-8v99-63c2
GitHub pull request 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-70470(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

These rows come from GitHub (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 14× in last 7d / 54× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 234 rows 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 134 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 20:03 UTCEchelonGraph re-scored
  2. 2026-11-21 20:03 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  3. 2026-11-21 16:41 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  4. 2026-11-20 21:41 UTCEchelonGraph re-scored
  5. 2026-11-20 21:40 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  6. 2026-11-20 16:38 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  7. 2026-11-19 23:18 UTCEchelonGraph re-scored
  8. 2026-11-19 23:18 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  9. 2026-11-19 16:35 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  10. 2026-11-19 00:03 UTCEchelonGraph re-scored
  11. 2026-11-19 00:03 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  12. 2026-11-18 16:35 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  13. 2026-11-18 01:41 UTCEchelonGraph re-scored
  14. 2026-11-18 01:41 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  15. 2026-11-17 16:35 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  16. 2026-11-17 03:20 UTCEchelonGraph re-scored
  17. 2026-11-17 03:20 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  18. 2026-11-16 16:52 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  19. 2026-11-16 04:55 UTCEchelonGraph re-scored
  20. 2026-11-16 04:55 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  21. 2026-11-15 17:02 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  22. 2026-11-15 05:01 UTCEchelonGraph re-scored
  23. 2026-11-15 05:00 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  24. 2026-11-14 16:41 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  25. 2026-11-14 06:38 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-14 06:38 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  2. 2026-11-13 16:57 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  3. 2026-11-13 08:01 UTCEchelonGraph re-scored
  4. 2026-11-13 08:01 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  5. 2026-11-12 16:34 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  6. 2026-11-12 09:39 UTCEchelonGraph re-scored
  7. 2026-11-12 09:39 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  8. 2026-11-11 16:40 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  9. 2026-11-11 11:17 UTCEchelonGraph re-scored
  10. 2026-11-11 11:17 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  11. 2026-11-10 16:45 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  12. 2026-11-10 12:55 UTCEchelonGraph re-scored
  13. 2026-11-10 12:55 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  14. 2026-11-09 16:36 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  15. 2026-11-09 14:33 UTCEchelonGraph re-scored
  16. 2026-11-09 14:33 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  17. 2026-11-08 16:40 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  18. 2026-11-08 16:12 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  19. 2026-11-07 17:46 UTCEchelonGraph re-scored
  20. 2026-11-07 17:46 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  21. 2026-11-07 16:39 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  22. 2026-11-06 19:24 UTCEchelonGraph re-scored
  23. 2026-11-06 19:24 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  24. 2026-11-06 16:39 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  25. 2026-11-06 16:25 UTCOSV refresh
  26. 2026-11-05 21:02 UTCEchelonGraph re-scored
  27. 2026-11-05 21:02 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  28. 2026-11-05 16:38 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  29. 2026-11-04 22:40 UTCEchelonGraph re-scored
  30. 2026-11-04 22:40 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  31. 2026-11-04 16:36 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  32. 2026-11-04 00:18 UTCEchelonGraph re-scored
  33. 2026-11-04 00:18 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  34. 2026-11-03 16:49 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  35. 2026-11-03 01:56 UTCEchelonGraph re-scored
  36. 2026-11-03 01:56 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  37. 2026-11-02 16:46 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  38. 2026-11-02 03:34 UTCEchelonGraph re-scored
  39. 2026-11-02 03:34 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  40. 2026-11-01 16:35 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  41. 2026-11-01 07:40 UTCGHSA enrichmentGHSA-52fh-8v99-63c2 · GitHub severity CRITICAL
  42. 2026-11-01 05:12 UTCEchelonGraph re-scored
  43. 2026-10-31 16:33 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  44. 2026-10-31 06:50 UTCEchelonGraph re-scored
  45. 2026-10-30 16:35 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  46. 2026-10-30 08:29 UTCEchelonGraph re-scored
  47. 2026-10-29 16:33 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  48. 2026-10-29 10:07 UTCEchelonGraph re-scored
  49. 2026-10-28 16:33 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  50. 2026-10-28 11:44 UTCEchelonGraph re-scored
  51. 2026-10-27 16:32 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  52. 2026-10-27 10:38 UTCEchelonGraph re-scored
  53. 2026-10-26 16:32 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  54. 2026-10-26 12:17 UTCEchelonGraph re-scored
  55. 2026-10-25 16:33 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  56. 2026-10-25 13:49 UTCEchelonGraph re-scored
  57. 2026-10-24 16:33 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  58. 2026-10-23 21:25 UTCEchelonGraph re-scored
  59. 2026-10-23 16:32 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  60. 2026-10-23 01:10 UTCEchelonGraph re-scored
  61. 2026-10-22 16:35 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  62. 2026-10-22 02:22 UTCEchelonGraph re-scored
  63. 2026-10-21 16:33 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  64. 2026-10-21 03:59 UTCEchelonGraph re-scored
  65. 2026-10-20 16:33 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  66. 2026-10-20 05:35 UTCEchelonGraph re-scored
  67. 2026-10-19 16:33 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  68. 2026-10-19 07:12 UTCEchelonGraph re-scored
  69. 2026-10-18 16:32 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  70. 2026-10-18 03:18 UTCEchelonGraph re-scored
  71. 2026-10-17 16:35 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  72. 2026-10-17 06:11 UTCEchelonGraph re-scored
  73. 2026-10-16 16:43 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  74. 2026-10-16 07:16 UTCEchelonGraph re-scored
  75. 2026-10-15 16:32 UTCEPSS rescoreEPSS 1.0% · 61st percentile

Frequently asked(5)

What is CVE-2026-70470?
CVE-2026-70470 is a critical-severity vulnerability; its CVE record was 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, Flowise validatePythonCodeForDataFrame in packages/components/src/pythonCodeValidator.ts can be bypassed with Unicode homoglyph identifiers, allowing arbitrary Python execution inside Pyodide…
When was the CVE record for CVE-2026-70470 published?
The CVE record for CVE-2026-70470 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 24, 2026; the record at its source may have been updated since.
Is CVE-2026-70470 actively exploited?
CVE-2026-70470 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (62nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-70470?
CVE-2026-70470 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-70470?
A fix for CVE-2026-70470 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-70470 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-70470

Explore →

Is Your Infrastructure Affected by CVE-2026-70470?

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