CVE Watchtower

CVE-2026-100610FlowiseAI Flowise Authorization Bypass Through User-Controlled Key

NVD

Vulnerability 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.
Severity Level
HIGH(7.7)
Published Date
Sep 26, 2026
Last Modified
Sep 28, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
0.35%Probability
Root Weakness (CWE)
The system does not prevent one user from accessing another user data or record by modifying the key value identifying the data.
CVSS v4.0 Base Metrics — Score 7.7 (HIGH)
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
Attack VectorNetwork
Attack ComplexityLow
Attack RequirementsPresent
Privileges RequiredLow
User InteractionNone
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)High
Availability (Vulnerable System)High
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None
Show CVSS v3.x metrics (score 7.5)
CVSS v3.1 Base Metrics — Score 7.5 (HIGH)
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

Affected & Patched Versions

Affected Versions
  • FlowiseAI Flowise <= 3.1.4
Patched Versions
  • FlowiseAI Flowise 3.1.4

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is high.

  1. Check whether you run FlowiseAI Flowise and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Sep 26, 2026Published
  • Sep 28, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new FlowiseAI Flowise CVEsYou are reading CVE-2026-100610. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More FlowiseAI Flowise CVEs

Data last checked: Nov 17, 2026 11:11 UTC