CVE-2026-70473

HIGHNVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 78% 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
Elevated
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.5Exploit: 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-and-drop user interface for building customized large language model (LLM) flows. Prior to 3.1.3, Flowise GET /api/v1/upsert-history returns the entire server-wide upsert history instead of being scoped to the requesting user, tenant, or workspace. The response can exceed 100MB and includes sensitive configuration data, including Vector Store settings such as Qdrant Server URL and collection name. The observed behavior indicates missing or insufficient authorization checks, workspace/project/tenant isolation, and pagination or limits, exposing integration parameters and infrastructure details that may enable further targeted attacks. This issue is fixed in version 3.1.3.

CVSS v3
8.5
EG Score
8.5(medium)
EG Risk
54(Track)
EG Risk 54/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
Severity85% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

August 4, 2026

Last Modified

September 11, 2026

Advisory Details (4)

Auto-updated Aug 4, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit, github_pr.
github Patch Available🟡 PoC Available

Information Disclosure in GET /api/v1/upsert-history returns the entire server-wide upsert history · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-fr6g-7cq8-fg82
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-146

Patch available: FlowiseAI/Flowise [email protected] (PR #6170 merged 2026-04-28)

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

commit d81483b70c99 (FlowiseAI/Flowise)

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

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

Vendor Advisories for CVE-2026-70473(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
flowise—3.1.3—

Weakness Classification(3)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-70473?
CVE-2026-70473 is a high 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 GET /api/v1/upsert-history returns the entire server-wide upsert history instead of being scoped to the requesting user, tenant, or workspace. The response can exceed 100MB…
When was CVE-2026-70473 disclosed?
CVE-2026-70473 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-70473 actively exploited?
CVE-2026-70473 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 77.6% of all scored CVEs.
What is the CVSS score of CVE-2026-70473?
CVE-2026-70473 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-70473?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-70473, 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-70473

Explore →

Is Your Infrastructure Affected by CVE-2026-70473?

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

Start Free Scan →Browse All CVEs