CVE-2025-71338

CRITICALNVD 9.810.0
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-26. NVD baseline CVSS 9.8; sources differ by 0.2.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2025-210343 (ENISA EUVD) · GHSA-c3hj-m5hq-59xw (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
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.2%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Flowise through 2.2.7 fails to sanitize path segments in the document-store loader endpoint, allowing unauthenticated attackers to write files outside the storage directory. Attackers can use parent-directory sequences to escape the storage directory and overwrite application files loaded at boot for remote code execution.

CVSS v3
9.8
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (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 yes (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.2%
EPSS %ILE
67th
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.2% 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 low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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 yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

June 25, 2026

Last Modified

October 12, 2026

Advisory Details (3)

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

Arbitrary file write to RCE · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-8vvx-qvq9-5948
Web page

Flowise - Arbitrary File Write to Remote Code Execution via document-store API | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-arbitrary-file-write-to-remote-code-execution-via-document-store-api
GitHub release Patch Available

flowise@2.2.7-patch.1

Patch available: FlowiseAI/Flowise flowise@2.2.7-patch.1

https://github.com/FlowiseAI/Flowise/releases/tag/flowise%402.2.7-patch.1

Vendor Advisories for CVE-2025-71338(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 rangeFix by version rangeDependents
flowise—
  • every version through 2.2.7: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 72× 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 99 of 512 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 413 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-71338?
CVE-2025-71338 is a critical-severity vulnerability; its CVE record was published on June 25, 2026. Flowise through 2.2.7 fails to sanitize path segments in the document-store loader endpoint, allowing unauthenticated attackers to write files outside the storage directory. Attackers can use parent-directory sequences to escape the storage directory and overwrite application files loaded at boot…
When was CVE-2025-71338 made public?
CVE-2025-71338 was made public on March 14, 2025: 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 June 25, 2026. EchelonGraph's copy of the record carries a last-modified date of October 12, 2026; the record at its source may have been updated since.
Is CVE-2025-71338 actively exploited?
CVE-2025-71338 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (67th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-71338?
CVE-2025-71338 has a CVSS v3 base score of 9.8 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 10.0 (CRITICAL).
How do I remediate CVE-2025-71338?
A fix for CVE-2025-71338 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-71338 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-2025-71338

Explore →

Is Your Infrastructure Affected by CVE-2025-71338?

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