Skip to content
Fencer Intel
critical 9.8

CVE-2025-26319 in the critical feed json

FlowiseAI Flowise arbitrary file upload vulnerability

published last yr. modified last mo. also GHSA-69jq-qr7w-j7qh , EUVD-2025-6168

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
55.9%
EPSS 55.9% chance of exploitation in 30 days, percentile 99%
public exploits
0
none known, plus a Nuclei check

Summary

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

Patch / fix

Is CVE-2025-26319 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

55.87% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template FlowiseAI Flowise <= 2.2.6 - Arbitrary File Upload nuclei detection template
  • github.com https://github.com/dorattias/CVE-2025-26319 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm flowise
<=2.2.6
 no fix listed

Classification

Weakness
  • CWE-434 Unrestricted Upload of File with Dangerous Type

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.