CVE-2026-56270
Unauthenticated access to /api/v1/loginmethod leaks SSO config and OAuth secrets.
Is CVE-2026-56270 being exploited?
Not confirmed. CVE-2026-56270 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 2.0% probability of exploitation in the next 30 days.
How severe is CVE-2026-56270?
CVE-2026-56270 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-56270?
Yes. A fix has been recorded for CVE-2026-56270. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-56270 affect?
CVE-2026-56270 affects Flowise Cloud (pre-3.1.0), Flowise self-hosted (pre-3.1.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-56270?
Patch to 3.1.0+; rotate OAuth secrets; audit SSO configs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can fetch org SSO config and OAuth client secrets (Google, Microsoft/Azure, GitHub, Auth0) via GET, enabling credential theft and OAuth abuse.
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.