---
id: CVE-2026-100610
title: >-
  Flowise through 3.1.4 exposes GET /api/v1/upsert-history/:id and PATCH
  /api/v1/upsert-history without route-level permission checks, and the backing
  service performs no workspace or ownership validation
summary: >-
  Flowise through 3.1.4 exposes GET /api/v1/upsert-history/:id and PATCH
  /api/v1/upsert-history without route-level permission checks, and the backing
  service performs no workspace or ownership validation. getAllUpsertHistory()
  returns Ups…
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'
cwe:
  - CWE-639
vendor: FlowiseAI
product: Flowise
affected:
  - Flowise <= 3.1.4
published: '2026-09-26'
updated: '2026-09-26'
sourceUpdated: '2026-09-26T14:16:41.570'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-100610'
references:
  - url: >-
      https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-jvx3-mjpw-r4gh
    label: disclosure@vulncheck.com
  - url: >-
      https://www.vulncheck.com/advisories/flowise-through-3.1.4-missing-authorization-via-upsert-history
    label: disclosure@vulncheck.com
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-26T13:33:20.932Z'
---

## Overview

Flowise through 3.1.4 exposes GET /api/v1/upsert-history/:id and PATCH /api/v1/upsert-history without route-level permission checks, and the backing service performs no workspace or ownership validation. getAllUpsertHistory() returns UpsertHistory rows selected solely by an attacker-supplied chatflowid, and patchDeleteUpsertHistory() deletes rows by an attacker-supplied array of record UUIDs. As a result, any authenticated low-privilege user or valid API key can read or delete document-store upsert history belonging to other users and other workspaces whenever the target chatflowId (which is exposed publicly in /chatbot/<chatflowId> share links) or row ids are known. The retrievable flowData and result fields contain embedding, record-manager and vector-store node configuration, including per-node paramValues. No patched version is available.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.