CVE-2026-70473 FlowiseAI CVE debrief

Who should care

Defenders and administrators of Flowise instances should assess exposure and prioritize remediation. This includes reviewing current configurations, verifying instance versions, and ensuring proper authorization controls are in place. Security teams and vulnerability management teams should also be aware of the potential risks and impacts of this vulnerability, especially in environments where Flowise is used to manage sensitive data or configurations

Why it matters

CVE-2026-70473 is a high-severity vulnerability in Flowise that exposes sensitive configuration data and upsert history. Defenders should prioritize remediation by updating to version 3.1.3 or later and restricting access to the Flowise API. The vulnerability's impact is limited to potential exposure and unauthorized access, but it does not support claims of exploitation, data theft, or outage.

• Potential exposure of sensitive configuration data
• Possible unauthorized access to upsert history
• Risk of targeted attacks using exposed infrastructure details
• Need for verification of Flowise instance version and configuration

Technical summary

The vulnerability in Flowise arises from the GET /api/v1/upsert-history endpoint, which returns server-wide upsert history without proper scoping to the user, tenant, or workspace. This results in exposure of sensitive configuration data, including Vector Store settings such as Qdrant Server URL and collection name. The response size can exceed 100MB, increasing the risk of unauthorized access and targeted attacks. The issue is addressed in Flowise version 3.1.3, which likely includes fixes for authorization checks and data access controls

Defensive priority

High

Recommended defensive actions

• Review and update Flowise to version 3.1.3 or later
• Restrict access to the Flowise API
• Monitor Flowise API usage for suspicious activity
• Verify Flowise instance configurations and authorization settings
• Conduct regular security audits and vulnerability assessments
• Implement compensating controls for exposed systems
• Track and document changes to Flowise configurations and API access

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. The issue is fixed in version 3.1.3 of Flowise. Evidence is based on CVE and NVD data, which indicate a high-severity vulnerability due to missing or insufficient authorization checks and workspace/project/tenant isolation. The observed behavior suggests exposure of integration parameters and infrastructure details, enabling further targeted attacks. Defenders should verify Flowise instance versions and configurations, focusing on authorization controls and data access

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.