CVE-2026-70473: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in FlowiseAI Flowise
Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. Prior to 3.1.3, Flowise GET /api/v1/upsert-history 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, including Vector Store settings such as Qdrant Server URL and collection name. The observed behavior indicates missing or insufficient authorization checks, workspace/project/tenant isolation, and pagination or limits, exposing integration parameters and infrastructure details that may enable further targeted attacks. This issue is fixed in version 3.1.3.
AI Analysis
Technical Summary
CVE-2026-70473 affects Flowise, a drag-and-drop interface for building LLM flows. Before version 3.1.3, the GET /api/v1/upsert-history endpoint returns the entire upsert history across the server rather than limiting data to the requesting user's scope. This results in exposure of sensitive configuration details, including integration parameters and infrastructure information like Vector Store settings (Qdrant Server URL and collection name). The flaw is due to missing or insufficient authorization checks and lack of tenant or workspace isolation, as well as absence of pagination or response size limits. The vulnerability is addressed in Flowise version 3.1.3.
Potential Impact
An attacker with access to the vulnerable endpoint can retrieve sensitive configuration data for the entire server, including integration parameters and infrastructure details. This exposure could facilitate further targeted attacks against the infrastructure or integrations. The large response size (over 100MB) may also impact service availability or performance during exploitation. There is no indication of privilege escalation or remote code execution from this vulnerability alone.
Mitigation Recommendations
This vulnerability is fixed in Flowise version 3.1.3. Users should upgrade to version 3.1.3 or later to remediate the issue. No vendor advisory is provided to indicate alternative mitigations or temporary fixes. Until upgraded, restrict access to the /api/v1/upsert-history endpoint to trusted users only and monitor for unusual access patterns.
CVE-2026-70473: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in FlowiseAI Flowise
Description
Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. Prior to 3.1.3, Flowise GET /api/v1/upsert-history 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, including Vector Store settings such as Qdrant Server URL and collection name. The observed behavior indicates missing or insufficient authorization checks, workspace/project/tenant isolation, and pagination or limits, exposing integration parameters and infrastructure details that may enable further targeted attacks. This issue is fixed in version 3.1.3.
CVSS v4.0
Score 8.3high
Affected software
FlowiseAI
Flowise
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-70473 affects Flowise, a drag-and-drop interface for building LLM flows. Before version 3.1.3, the GET /api/v1/upsert-history endpoint returns the entire upsert history across the server rather than limiting data to the requesting user's scope. This results in exposure of sensitive configuration details, including integration parameters and infrastructure information like Vector Store settings (Qdrant Server URL and collection name). The flaw is due to missing or insufficient authorization checks and lack of tenant or workspace isolation, as well as absence of pagination or response size limits. The vulnerability is addressed in Flowise version 3.1.3.
Potential Impact
An attacker with access to the vulnerable endpoint can retrieve sensitive configuration data for the entire server, including integration parameters and infrastructure details. This exposure could facilitate further targeted attacks against the infrastructure or integrations. The large response size (over 100MB) may also impact service availability or performance during exploitation. There is no indication of privilege escalation or remote code execution from this vulnerability alone.
Mitigation Recommendations
This vulnerability is fixed in Flowise version 3.1.3. Users should upgrade to version 3.1.3 or later to remediate the issue. No vendor advisory is provided to indicate alternative mitigations or temporary fixes. Until upgraded, restrict access to the /api/v1/upsert-history endpoint to trusted users only and monitor for unusual access patterns.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-04T15:24:41.339Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a723098bf8831d5393f8de3
Added to database: 08/04/2026, 18:34:00 UTC
Last enriched: 08/04/2026, 18:41:28 UTC
Last updated: 09/18/2026, 10:01:33 UTC
Views: 61
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.