CVE-2026-56271
Hardcoded default JWT secrets in Flowise allow token forgery and authentication bypass.
Is CVE-2026-56271 being exploited?
Not confirmed. CVE-2026-56271 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.66% probability of exploitation in the next 30 days.
How severe is CVE-2026-56271?
CVE-2026-56271 is rated Critical with a CVSS score of 9.3. 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-56271?
Yes. A fix has been recorded for CVE-2026-56271. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-56271 affect?
CVE-2026-56271 affects Flowise <= 3.0.13, Flowise server enterprise passport middleware, Apps using Flowise enterprise auth. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-56271?
Upgrade to Flowise 3.1.0; set strong JWT secrets and rotate affected tokens.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can forge JWTs to impersonate any user, including administrators, enabling complete auth bypass and account takeover.
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.