CVE-2026-70471

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 83% 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
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: 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 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.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

August 4, 2026

Last Modified

September 14, 2026

Advisory Details (2)

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

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

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

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.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
flowise3.1.3

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-70471?
CVE-2026-70471 is a medium vulnerability 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 CVE-2026-70471 disclosed?
CVE-2026-70471 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-70471 actively exploited?
CVE-2026-70471 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.9% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-70471, 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-70471

Explore →

Is Your Infrastructure Affected by CVE-2026-70471?

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