CVE-2026-70478
Unauthenticated endpoint returns refreshed OAuth access_tokens in Flowise <3.1.3
Is CVE-2026-70478 being exploited?
Not confirmed. CVE-2026-70478 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.53% probability of exploitation in the next 30 days.
How severe is CVE-2026-70478?
CVE-2026-70478 is rated Critical with a CVSS score of 9.2. 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-70478?
Yes. A fix has been recorded for CVE-2026-70478. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-70478 affect?
CVE-2026-70478 affects Flowise < 3.1.3, POST /api/v1/oauth2-credential/refresh/:credentialId. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-70478?
Upgrade to Flowise 3.1.3, rotate OAuth secrets/tokens, restrict/authenticate the endpoint.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated POST returns decrypted refreshed OAuth access_token; attacker with a credential ID can access connected services and exhaust refresh-token quota.
Immediate action required
- affected< 3.1.2
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.