CVE-2026-70473
Authorization flaw exposes server-wide upsert history and vector-store config.
Is CVE-2026-70473 being exploited?
Not confirmed. CVE-2026-70473 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.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-70473?
CVE-2026-70473 is rated High with a CVSS score of 8.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-70473?
Yes. A fix has been recorded for CVE-2026-70473. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-70473 affect?
CVE-2026-70473 affects Flowise versions prior to 3.1.3 (GET /api/v1/upsert-history). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-70473?
Upgrade to Flowise 3.1.3, restrict access, rotate any exposed credentials/endpoints.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Insufficient authorization allows access to server-wide upsert history revealing vector-store URLs, collection names and config; enables infrastructure discovery, credential exposure and targeted attacks.
Immediate action required
- affected< 3.1.3
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.