CVE-2025-26319

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because EPSS predicts 89% probability of exploitation within the next 30 days (top 0.5% of all CVEs). NVD baseline CVSS 9.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 51%
CISA-KEV: Not listedEPSS: 51%CVSS: 9.8Exploit: NoneExposed: 0

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

FlowiseAI Flowise v2.2.6 was discovered to contain an arbitrary file upload vulnerability in /api/v1/attachments.

CVSS v3
9.8
EG Score
9.8(high)
EPSS
98.8%
KEV
Not listed

Published

March 4, 2025

Last Modified

June 24, 2025

Advisory Details (1)

Auto-updated Jun 8, 2026
No patch confirmed yet.
generic

GitHub - dorattias/CVE-2025-26319 · GitHub

https://github.com/dorattias/CVE-2025-26319

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
npmflowise—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 rangeFixed inDependents
flowise———

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 35× 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-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 01:59 UTCEPSS rescore
  4. 2026-07-13 06:12 UTCEPSS rescore
  5. 2026-07-13 06:12 UTCEPSS rescore
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-12 05:46 UTCEPSS rescore
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-11 08:26 UTCEPSS rescore
  10. 2026-07-09 19:09 UTCEPSS rescore
  11. 2026-07-08 15:14 UTCEPSS rescore
  12. 2026-07-07 08:21 UTCOSV refresh
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-01 15:06 UTCEPSS rescore
  15. 2026-06-30 23:21 UTCEPSS rescore
  16. 2026-06-30 23:21 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-28 04:55 UTCEPSS rescore
  19. 2026-06-28 04:55 UTCEPSS rescore
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-25 13:49 UTCEPSS rescore
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-23 21:32 UTCEPSS rescore
  25. 2026-06-23 21:32 UTCEPSS rescore
Show 30 more
  1. 2026-06-22 14:25 UTCEPSS rescore
  2. 2026-06-22 14:25 UTCEPSS rescore
  3. 2026-06-21 01:59 UTCEPSS rescore
  4. 2026-06-21 01:59 UTCEPSS rescore
  5. 2026-06-18 19:35 UTCOSV refresh
  6. 2026-06-18 17:52 UTCEPSS rescore
  7. 2026-06-18 17:52 UTCEPSS rescore
  8. 2026-06-17 17:52 UTCEPSS rescore
  9. 2026-06-16 17:52 UTCEPSS rescore
  10. 2026-06-16 17:52 UTCEPSS rescore
  11. 2026-06-15 17:48 UTCEPSS rescore
  12. 2026-06-13 22:59 UTCEPSS rescore
  13. 2026-06-12 23:11 UTCEPSS rescore
  14. 2026-06-10 22:18 UTCEPSS rescore
  15. 2026-06-08 14:16 UTCEPSS rescore
  16. 2026-06-08 14:16 UTCEPSS rescore
  17. 2026-06-07 15:24 UTCEPSS rescore
  18. 2026-06-07 15:24 UTCEPSS rescore
  19. 2026-06-05 22:46 UTCEPSS rescore
  20. 2026-06-05 22:46 UTCEPSS rescore
  21. 2026-06-04 13:11 UTCEPSS rescore
  22. 2026-06-04 13:11 UTCEPSS rescore
  23. 2026-06-01 13:51 UTCEPSS rescore
  24. 2026-06-01 13:51 UTCEPSS rescore
  25. 2026-05-31 00:16 UTCEPSS rescore
  26. 2026-05-31 00:16 UTCEPSS rescore
  27. 2026-05-30 10:09 UTCEG score recompute
  28. 2026-05-30 10:09 UTCGHSA enrichment
  29. 2026-05-30 07:59 UTCOSV refresh
  30. 2026-05-29 13:44 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2025/CVE-2025-26319.yaml
    First seen Jan 1, 2025

    FlowiseAI Flowise <= 2.2.6 - Arbitrary File Upload

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-26319?
CVE-2025-26319 is a critical vulnerability published on March 4, 2025. FlowiseAI Flowise v2.2.6 was discovered to contain an arbitrary file upload vulnerability in /api/v1/attachments.
When was CVE-2025-26319 disclosed?
CVE-2025-26319 was first published in the National Vulnerability Database on March 4, 2025, with the most recent update on June 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-26319 actively exploited?
CVE-2025-26319 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-26319?
CVE-2025-26319 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-26319?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-26319, 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-2025-26319

Explore →

Is Your Infrastructure Affected by CVE-2025-26319?

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

Start Free Scan →Browse All CVEs