What happened
Published 2026-09-26 (CVSS 7.5 v3.1): Flowise exposes upsert-history read and delete routes with no route-level permission check and no workspace/ownership validation; retrievable flowData includes per-node paramValues (vector-store and embedding configuration), enabling cross-tenant disclosure and deletion in RAG pipelines.
Why it matters
Flowise is a leading no-code RAG/agent builder; the leaked node config and destroyed ingestion history live in the document-store layer that powers retrieval (and can expose embeddings infrastructure config and secrets in paramValues) across tenants of a shared Flowise deployment.
Attack vector
Authenticated user calls the unauthenticated-checked GET /api/v1/upsert-history/:id and PATCH /api/v1/upsert-history with a known chatflowId (exposed in share links) or row UUIDs; no workspace or ownership validation is performed, so other tenants' RAG document-store ingestion history and node configuration leak or are destroyed.
Affected systems
Flowise <= 3.1.4 (GET/PATCH /api/v1/upsert-history endpoints).
Mitigation
No patched version is available at publication (2026-09-26); restrict access to the affected routes via a reverse proxy/API gateway and revoke unnecessary low-privilege API keys until a fix ships.