Flowise Upsert History Endpoint Missing Authorization Checks

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.

Casky was already ahead

This CVE exploits attack patterns that Casky's 283matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

CVE-2026-100610 is an authorization bypass vulnerability affecting Flowise versions through 3.1.4 that exposes document management endpoints without proper permission validation. The GET and PATCH endpoints for upsert history lack route-level checks and the backend service performs no workspace or ownership validation, allowing any authenticated user—even with minimal privileges—to read or delete document store records belonging to other users or workspaces. This vulnerability affects organizations using Flowise for document processing and retrieval, potentially exposing sensitive documents to unauthorized access and deletion by low-privilege users or compromised API keys.

Casky's 283 matched security skills, powered by Claude AI's extended reasoning capabilities, correlate this vulnerability across two primary MITRE ATT&CK tactics: TA0004 (Privilege Escalation) and TA0006 (Credential Access). Practitioners using Casky would identify attack patterns including: (1) unauthorized lateral access to document repositories through privilege escalation techniques—detecting when low-privilege accounts suddenly enumerate or modify high-value upsert history records across different chatflows and workspaces, and (2) credential access risks where compromised or lower-privilege API keys become vectors for mass document exfiltration. The skill set would surface indicators such as anomalous cross-workspace API calls to /upsert-history endpoints, batch deletion patterns of records not owned by the requesting user, and authorization failures that bypass expected permission controls—enabling detection of both reconnaissance and exploitation phases before sensitive data loss occurs.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

283 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-100610.

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

Access with Stolen Session Cookie

identity access management · low

Run

MITRE ATT&CK Techniques

TA0004 TA0006

Investigate the attack patterns behind CVE-2026-100610

Casky has 283 skills that investigate the attack patterns behind CVE-2026-100610. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn