CVE-2026-41278
Public API endpoints expose raw chatflow data including credentials.
Is CVE-2026-41278 being exploited?
Not confirmed. CVE-2026-41278 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 0.42% probability of exploitation in the next 30 days.
How severe is CVE-2026-41278?
CVE-2026-41278 is rated High with a CVSS score of 8.7. 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-41278?
Yes. A fix has been recorded for CVE-2026-41278. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41278 affect?
CVE-2026-41278 affects Flowise pre-3.1.0 public endpoints. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41278?
Upgrade to 3.1.0+ to fix exposure
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated GET on public endpoints leaks credential IDs, plaintext API keys, and passwords in chatflow data.
Patch when possible
- 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.