FlowiseAI Flowise up to 3.1.4 Upsert History /api/v1/upsert-history getAllUpsertHistory/patchDeleteUpsertHistory chatflowId/row ids permission

Summaryinfo

A vulnerability identified as critical has been detected in FlowiseAI Flowise up to 3.1.4. Affected is the function getAllUpsertHistory/patchDeleteUpsertHistory of the file /api/v1/upsert-history of the component Upsert History. This manipulation of the argument chatflowId/row ids causes permission. The identification of this vulnerability is CVE-2026-100610. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability has been found in FlowiseAI Flowise up to 3.1.4 and classified as critical. Affected by this vulnerability is the function getAllUpsertHistory/patchDeleteUpsertHistory of the file /api/v1/upsert-history of the component Upsert History. The manipulation of the argument chatflowId/row ids with an unknown input leads to a permission vulnerability. The CWE definition for the vulnerability is CWE-275. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-100610 since 09/26/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/26/2026). MITRE ATT&CK project uses the attack technique T1222 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• FlowiseAI

Name

• Flowise

Version

• 3.1.0
• 3.1.1
• 3.1.2
• 3.1.3
• 3.1.4

Website

• Product: https://github.com/FlowiseAI/Flowise/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion