CVE-2026-100610
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
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 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.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| FlowiseAI | Flowise | 0 <= 3.1.4 | affected |
Weaknesses
- CWE-639: Authorization Bypass Through User-Controlled Key
References
- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-jvx3-mjpw-r4gh
- https://www.vulncheck.com/advisories/flowise-through-3.1.4-missing-authorization-via-upsert-history
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.