Auth bypass in Flowiseai Flowise
CVE-2026-100610
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.
Vulnerability class: IDOR (Insecure Direct Object Reference)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- github.com/FlowiseAI/Flowise/security/advisories/GHSA-jvx3-mjpw-r4gh (vendor-advisory)
- www.vulncheck.com/advisories/flowise-through-3.1.4-missing-authorization-via-up… (third-party-advisory)
Frequently asked questions
- What is CVE-2026-100610?
- CVE-2026-100610 is a high-severity vulnerability in Flowiseai Flowise, classified under Authorization Bypass Through User-Controlled Key. CVSS score: 7.5/10. Published 2026-09-26.
- How severe is CVE-2026-100610?
- High severity. CVSS v3 base score is 7.5 out of 10.