CVE-2026-70471

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.4% (36th 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

Also known asEUVD-2026-52850 (ENISA EUVD) · GHSA-8r8h-6vcc-xhrv (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: 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 3.1.3, Flowise injects $vars into the code execution sandbox without requiring variables:view, bypassing the permission-protected Variables API. Variables for the active workspace are fetched at packages/components/src/utils.ts and runtime variables are resolved from server environment variables, while the official variables route enforces variables:view. A user or API key that is denied variables:view can call /api/v1/node-custom-function and receive $vars pre-populated with all variables for the workspace, including Variable.name to Variable.value static variables and Variable.name to process.env[Variable.name] runtime variables. This can expose secrets such as database passwords, JWT secrets, SMTP passwords, and cloud keys, depending on the workspace Variables configuration. This issue is fixed in version 3.1.3.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.4%
EPSS %ILE
36th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-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.4% 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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 (2)

Auto-updated Aug 4, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

RBAC Bypass Leading to Unauthorized Workspace Variables Disclosure · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-8r8h-6vcc-xhrv
GitHub release Patch Available

[email protected]

Patch available: FlowiseAI/Flowise [email protected]

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

Vendor Advisories for CVE-2026-70471(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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
flowise—
  • 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 7× in last 7d / 31× 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 163 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 63 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-70471?
CVE-2026-70471 is a medium-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 3.1.3, Flowise injects $vars into the code execution sandbox without requiring variables:view, bypassing the permission-protected Variables API. Variables for the active workspace are…
When was the CVE record for CVE-2026-70471 published?
The CVE record for CVE-2026-70471 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-70471 actively exploited?
CVE-2026-70471 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-70471?
CVE-2026-70471 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-70471?
A fix for CVE-2026-70471 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-70471 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-70471

Explore →

Is Your Infrastructure Affected by CVE-2026-70471?

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

Book a Demo →Browse All CVEs