CVE-2026-100610
Deferred Deferred - Pending Action

Flowise Unauthorized Data Access via Missing Permission Checks

Publication date: 2026-09-26

Last updated on: 2026-09-26

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-26
Last Modified
2026-09-26
Generated
2026-09-26
AI Q&A
2026-09-26
EPSS Evaluated
N/A
NVD
CVE-2026-100610
EUVD
EUVD-2026-87705

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
flowise flowise to 3.1.4 (exc)
flowiseai flowise to 3.1.4 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Flowise versions 3.1.4 and earlier allows authenticated users or API keys to read or delete document-store upsert history across workspaces without proper authorization checks. The endpoints GET /api/v1/upsert-history/:id and PATCH /api/v1/upsert-history lack route-level permission checks and workspace validation. Attackers can exploit this by using a known chatflowId, which is exposed in public chatbot links, to access or delete sensitive configuration data like embedding, record-manager, and vector-store node settings.

Detection Guidance

Check Flowise API endpoints for unauthorized access to /api/v1/upsert-history/:id or PATCH /api/v1/upsert-history. Monitor logs for GET/PATCH requests with unusual chatflowId or UUID parameters. Verify if users can access or delete history data outside their workspace.

Impact Analysis

This vulnerability can lead to confidentiality and integrity breaches. Attackers can read or delete audit and troubleshooting data across workspace boundaries, exposing sensitive configuration details such as embedding, record-manager, and vector-store node settings. Since chatflowId values are publicly exposed, any low-privilege authenticated user or valid API key can perform these unauthorized actions.

Compliance Impact

This vulnerability can severely impact compliance with GDPR and HIPAA by enabling unauthorized access to and deletion of sensitive data. GDPR requires protecting personal data, and HIPAA mandates safeguarding protected health information. Unauthorized access or deletion of audit logs and configuration data could result in non-compliance, potential data breaches, and legal consequences.

Mitigation Strategies

Immediately restrict access to /api/v1/upsert-history endpoints via network policies or WAF rules. Disable or audit API keys for unauthorized use. Monitor for suspicious GET/PATCH requests targeting these endpoints. Consider isolating Flowise instances until a patch is available.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-100610. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart