CVE-2026-70473 FlowiseAI CVE debrief

Who should care

Defenders of Flowise installations, particularly those with multiple users, tenants, or workspaces, should assess their exposure and prioritize updating to version 3.1.3 or later. Security teams responsible for LLM flow deployments should review their configurations and implement proper authorization checks to prevent unauthorized access to upsert history.

Why it matters

CVE-2026-70473 in Flowise allows unauthorized access to server-wide upsert history, exposing sensitive data and potentially enabling targeted attacks. Defenders should prioritize updating to version 3.1.3, implement proper authorization checks, and review configurations to prevent exposure.

• Potential exposure of sensitive configuration data, including Vector Store settings.
• Possible unauthorized access to upsert history across different users, tenants, or workspaces.
• Risk of targeted attacks using exposed integration parameters and infrastructure details.
• Need for verification of affected versions and remediation efforts.

Technical summary

Flowise, a drag-and-drop user interface for building customized large language model (LLM) flows, has a vulnerability in its API endpoint GET /api/v1/upsert-history. Prior to version 3.1.3, this endpoint returns the entire server-wide upsert history instead of being scoped to the requesting user, tenant, or workspace. The response can exceed 100MB and includes sensitive configuration data, such as Vector Store settings like Qdrant Server URL and collection name. This issue is due to missing or insufficient authorization checks, workspace/project/tenant isolation, and pagination or limits.

Defensive priority

High

Recommended defensive actions

• Review and update Flowise to version 3.1.3 or later
• Restrict access to the GET /api/v1/upsert-history endpoint
• Implement proper authorization checks and workspace/project/tenant isolation
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in Flowise, a drag-and-drop user interface for building customized large language model (LLM) flows. Prior to version 3.1.3, the GET /api/v1/upsert-history endpoint returns the entire server-wide upsert history, including sensitive configuration data, instead of being scoped to the requesting user, tenant, or workspace.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.