Flowise: Information Disclosure in GET /api/v1/upsert-history returns the entire server-wide upsert…
Flowise
More for Flowise RSS feed for Flowise
- Severity
- High, CVSS 8.5
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
- Record
- CVE-2026-70473
- Affects
- Flowise
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- August 4, 2026
- Source last modified
- October 24, 2026
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.
Description quoted from the NVD record.
Who is affected
Flowise is a drag-and-drop tool for building apps that use AI language models. This flaw affects versions before 3.1.3. A user who asks a part of the product for the history of data loaded into the app gets back that history for the whole server, not just for their own account, team or workspace. The reply can be very large and includes sensitive settings, such as the address and collection name of databases that store information for the AI. An attacker could use these details to plan further targeted attacks. This flaw is rated High.
What to do
- Find out who runs Flowise for your organization: the person who installed it, or the IT provider or vendor who manages it.
- If you or your staff run it yourselves, update Flowise to version
3.1.3or later, which fixes this flaw. - If an IT provider or vendor runs it for you, send them this advisory and ask when the update to version
3.1.3will be done. - If your organization does not use Flowise, this flaw does not affect you and no action is needed.
Analysis written from the source record as of October 24, 2026 and reviewed before publishing.