CVE-2026-70473
Received Received - Intake

Flowise Information Disclosure via Unauthorized API Access

Publication date: 2026-08-04

Last updated on: 2026-08-04

Assigner: GitHub, Inc.

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-04
Last Modified
2026-08-04
Generated
2026-08-04
AI Q&A
2026-08-04
EPSS Evaluated
N/A
NVD
CVE-2026-70473
EUVD
EUVD-2026-52853

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
flowise flowise 3.1.3
flowiseai flowise to 3.1.3 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
CWE-202 When trying to keep information confidential, an attacker can often infer some of the information by using statistics.
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-70473 is an information disclosure vulnerability in Flowise versions before 3.1.3. The GET /api/v1/upsert-history endpoint returns the entire server-wide upsert history instead of being scoped to the requesting user or tenant. This exposes sensitive configuration data such as Vector Store settings, including Qdrant Server URLs and collection names. The issue stems from missing authorization checks and insufficient data scoping.

Detection Guidance

Check if your Flowise instance is running a version prior to 3.1.3 by inspecting the version in the application or logs. Test the GET /api/v1/upsert-history endpoint by sending a request to see if it returns excessive data exceeding 100MB or includes sensitive configuration details like Qdrant Server URLs.

Impact Analysis

An attacker can exploit this by making a simple API request to retrieve sensitive infrastructure details, enabling reconnaissance and potential follow-up attacks. The exposed data includes Vector Store settings like Qdrant Server URLs and collection names, which could be used to gain further access or disrupt services.

Mitigation Strategies

Upgrade Flowise to version 3.1.3 or later to apply the security fixes. Ensure all endpoints enforce workspace and tenant scoping by validating workspace IDs and implementing proper authorization checks. Review and restrict access to sensitive endpoints like /api/v1/upsert-history.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-70473. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart