CVE-2026-71962

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan mitigationRemediate 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: 0.7%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists FlowiseAI Flowise versions 2.2.4 up to and including 3.1.4 as affected. No release containing a fix is confirmed on record.

Flowise versions 2.2.4 through 3.1.4 contain a missing authorization vulnerability in the POST /api/v1/openai-assistants-file/download endpoint that allows unauthenticated attackers to access private files by exploiting the endpoint's inclusion in the global authentication whitelist, which bypasses all session and API key verification. Attackers can supply valid chatflowId, chatId, and fileName identifiers to retrieve files from any chatflow on the instance, including private chatflows belonging to other workspaces or organizations.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 10, 2026

Last Modified

September 4, 2026

Advisory Details (3)

Auto-updated Aug 10, 2026
No fix on record yet.
Web page

Flowise 2.2.4 - 3.1.4 Missing Authorization via openai-assistants-file/download | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-missing-authorization-via-openai-assistants-file-download
Web page

The Future of Flowise

https://flowiseai.com/sunset
Web page

CVE-2026-71962.md · GitHub

https://gist.github.com/haidang-infosec/402db84bee7aca2f57bb109b31574649?utm_source=chatgpt.com

Vendor Advisories for CVE-2026-71962(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 84× 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 it from the CNA feed. 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). Most recent first.

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71962?
CVE-2026-71962 is a high-severity vulnerability; its CVE record was published on August 10, 2026. Flowise versions 2.2.4 through 3.1.4 contain a missing authorization vulnerability in the POST /api/v1/openai-assistants-file/download endpoint that allows unauthenticated attackers to access private files by exploiting the endpoint's inclusion in the global authentication whitelist, which bypasses…
When was CVE-2026-71962 made public?
CVE-2026-71962 was made public on August 10, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 10, 2026. EchelonGraph's copy of the record carries a last-modified date of September 4, 2026; the record at its source may have been updated since.
Is CVE-2026-71962 actively exploited?
CVE-2026-71962 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71962?
CVE-2026-71962 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71962?
No fix for CVE-2026-71962 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists FlowiseAI Flowise versions 2.2.4 up to and including 3.1.4 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-71962 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-71962

Explore →

Is Your Infrastructure Affected by CVE-2026-71962?

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

Book a Demo →Browse All CVEs