CVE-2026-41268
Unauthenticated RCE in Flowise before 3.1.0 via FILE-STORAGE:: and NODE_OPTIONS.
Is CVE-2026-41268 being exploited?
Not confirmed. CVE-2026-41268 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 14% probability of exploitation in the next 30 days.
How severe is CVE-2026-41268?
CVE-2026-41268 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-41268?
Yes. A fix has been recorded for CVE-2026-41268. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41268 affect?
CVE-2026-41268 affects Flowise (prior to 3.1.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41268?
Upgrade to Flowise 3.1.0+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated RCE with root privileges in Flowise container via crafted HTTP request using FILE-STORAGE:: and NODE_OPTIONS.
Immediate action required
- affected< 3.1.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.