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.
References
Configurations
No configuration.
History
28 Sep 2026, 19:16
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-jvx3-mjpw-r4gh - |
26 Sep 2026, 14:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-09-26 14:16
Updated : 2026-09-28 19:16
NVD link : CVE-2026-100610
Mitre link : CVE-2026-100610
CVE.ORG link : CVE-2026-100610
JSON object : View
Products Affected
No product.
CWE
CWE-639
Authorization Bypass Through User-Controlled Key
