CVE-2026-70473

Flowise before 3.1.3 fails to enforce authorization on the GET /api/v1/upsert-history endpoint, which returns the entire server-wide upsert history instead of records scoped to the requesting user, tenant, or workspace (CWE-862, CWE-200). An authenticated low-privileged user can trigger the flaw with a single HTTP GET request, and because no pagination or limits are applied, responses can exceed 100MB. An attacker gains sensitive configuration data, including Vector Store settings such as the Qdrant server URL and collection name, which can enable targeted follow-up attacks against the underlying infrastructure. All Flowise deployments prior to 3.1.3 are affected, with multi-user or multi-tenant instances at greatest risk. No in-the-wild exploitation has been reported (EPSS 0.3%, not in CISA KEV), though a public security advisory is available.

What to do: Upgrade to Flowise 3.1.3 or later. Until patched, restrict or block access to /api/v1/upsert-history at a reverse proxy and check access logs for unusually large responses from that endpoint. Review whether Vector Store details (e.g., Qdrant server URLs and collections) were exposed and rotate or restrict credentials for those backends.