Which versions of Flowise are affected by CVE-2026-67621?

Flowise AI workflow platform (versions through 3.1.4) contains an authorization bypass allowing authenticated workspace members with view-only permissions to directly modify vector databases and…

How to fix or mitigate CVE-2026-67621?

Within 24 hours, audit all view-only workspace member accounts and review document store audit logs for unauthorized mutations on upsert and refresh endpoints. Within 7 days, restrict mutation endpoint access to administrative roles only through role-based access policies and network-level controls, and enable detailed logging on all document store operations. Within 30 days, monitor vendor advisories for patches, validate any available fixes in non-production environments, and implement additional server-side authorization validation on document store endpoints if self-hosted.

Flowise CVE-2026-67621

Q: What is the CVSS score of CVE-2026-67621?

CVE-2026-67621 has a CVSS 4.0 base score of 7.2 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.2%.

EUVD-2026-54169 HIGH

Missing Authorization (CWE-862)

2026-08-06 disclosure@vulncheck.com

GHSA-7q53-9j99-gg5c

Authentication Bypass Flowise Flowiseai

7.2

CVSS 4.0 · Vendor: vulncheck

Severity by source

Vendor (vulncheck) PRIMARY

7.2 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

7.6 HIGH

Network-accessible endpoints require only low-privilege workspace membership; high integrity impact from unrestricted vector store writes; low confidentiality and availability from potential data exposure and API credit exhaustion.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (vulncheck).

CVSS VectorVendor: vulncheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Aug 06, 2026 - 22:49 vuln.today

CVE Published

Aug 06, 2026 - 22:18 cve.org

HIGH 7.2

DescriptionCVE.org

Flowise through 3.1.4 contains a missing authorization vulnerability that allows authenticated workspace members to perform unauthorized document store operations by accessing unprotected mutation endpoints. Attackers holding only view-level permissions can send direct HTTP requests to the upsert and refresh document store routes to trigger document ingestion, refresh vector database contents, consume embedding API credits, and modify knowledge bases used by downstream chatflows.

AnalysisAI

Flowise through version 3.1.4 exposes document store mutation endpoints without enforcing authorization, allowing authenticated workspace members holding only view-level permissions to directly invoke upsert and refresh routes that should be restricted to higher-privileged roles. The missing server-side authorization check (CWE-862) enables a malicious insider or compromised view-only account to inject or overwrite vector database contents, trigger costly embedding API credit consumption, and corrupt knowledge bases that power downstream AI chatflows - without any UI-layer interaction. No public exploit has been identified at time of analysis, though the exploitation path is low-complexity given direct HTTP access suffices, and a disclosure advisory is publicly available on GitHub.

Technical ContextAI

Flowise is an open-source, low-code platform for constructing LLM-orchestration pipelines and retrieval-augmented generation (RAG) workflows. Its document store subsystem manages ingestion of documents into vector databases, which are queried at inference time by downstream chatflows. The flaw (CWE-862: Missing Authorization) is in the mutation layer of this subsystem: the API routes handling upsert (document ingestion into the vector store) and refresh (reprocessing and re-embedding stored documents) perform no server-side permission check beyond confirming the caller is an authenticated workspace member. The CVSS 4.0 vector AV:N/AC:L/AT:N/PR:L confirms network-accessible endpoints with low privilege and no attack requirements. In a correctly implemented RBAC system, write operations on the document store would be gated on a higher permission tier than the view role; here, authentication and authorization are conflated, leaving mutation endpoints effectively open to any workspace member.

RemediationAI

Upgrade Flowise to a version beyond 3.1.4 that addresses this authorization gap; however, no specific patched release version was confirmed from the available input data - verify the current release on the official Flowise GitHub repository before upgrading. Given the reference to https://flowiseai.com/sunset potentially signaling end-of-life status, organizations should assess whether continued operation of Flowise is appropriate or whether migration to a supported LLM workflow platform is warranted. As immediate compensating controls: restrict access to document store mutation routes (e.g., /api/v1/document-store/upsert and equivalent refresh endpoints) at the API gateway or reverse proxy layer to only trusted administrator IP ranges - this prevents exploitation with no application-layer change but requires correct network topology. Additionally, audit all workspace members and revoke view-only access for untrusted or unnecessary accounts to reduce the pool of potential exploiters. Monitor embedding API usage logs for unexpected ingestion volume spikes, which may indicate unauthorized calls. Advisory: https://github.com/Caycon/cve-advisories/blob/main/2026/Flowise/CVE-2026-67621.md.