CVE-2026-100610 Flowise through 3.1.4 Missing Authorization via upsert-history
Authenticated users can read or delete other users' upsert history and configuration data due to missing authorization checks in Flowise.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-100610?
CVE-2026-100610 is a high-severity missing authorization vulnerability in FlowiseAI Flowise, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-639
Which versions are affected by CVE-2026-100610?
How do I fix CVE-2026-100610?
No fix has been published for CVE-2026-100610 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-100610 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100610 exists.
Sources
Also known as GHSA-jvx3-mjpw-r4gh, GHSA-r2p4-x7cc-x3mm.