Which versions of Flowise are affected by EUVD-2026-52871?

Flowise workflow automation deployments prior to version 3.1.3 contain a privilege escalation vulnerability allowing any authenticated workspace member to bypass role-based access controls and modify…. A patch is available.

How to fix or mitigate EUVD-2026-52871?

Within 24 hours, identify all Flowise instances running versions prior to 3.1.3 and prioritize production deployments for immediate action. Within 7 days, upgrade all affected instances to version 3.1.3 or later, testing thoroughly in staging environments first to validate compatibility with existing workflows. Within 30 days, conduct a comprehensive audit of execution modification logs from the past 90 days to identify any unauthorized changes, document findings, and confirm no malicious activity has occurred.

Flowise EUVD-2026-52871

Q: What is the CVSS score of EUVD-2026-52871?

EUVD-2026-52871 has a CVSS 4.0 base score of 7.1 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/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.3%.

| CVE-2026-70475 HIGH

Missing Authorization (CWE-862)

2026-08-04 GitHub_M

GHSA-fm2f-4339-4p2f

Privilege Escalation Authentication Bypass Flowise

7.1

CVSS 4.0 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

7.1 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/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

6.5 MEDIUM

Network-accessible endpoint requires a valid account (PR:L); RBAC is never invoked so any authenticated user succeeds; only integrity of execution records is impacted, with no confidentiality or availability consequence.

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

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

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Aug 04, 2026 - 20:01 EUVD

Source Code Evidence Fetched

Aug 04, 2026 - 19:51 vuln.today

Analysis Generated

Aug 04, 2026 - 19:51 vuln.today

CVE Published

Aug 04, 2026 - 19:18 cve.org

HIGH 7.1

DescriptionCVE.org

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, the PUT /api/v1/executions/:id endpoint in packages/server/src/routes/executions/index.ts lacks the checkAnyPermission() middleware that protects other execution endpoints. Any authenticated user, regardless of assigned permissions, can modify execution state, data, and metadata of any execution in their workspace, enabling privilege escalation and manipulation of workflow execution results. This issue is fixed in 3.1.3.

AnalysisAI

Missing authorization middleware on the PUT /api/v1/executions/:id endpoint in Flowise prior to 3.1.3 allows any authenticated workspace member, regardless of assigned RBAC role, to overwrite execution state, data, and metadata for any workflow execution in their workspace. The flaw is a straightforward RBAC enforcement gap - the checkAnyPermission() middleware present on all sibling GET and DELETE routes was omitted from the PUT handler - making privilege escalation trivially reproducible with a single authenticated API call. No confirmed active exploitation (not in CISA KEV), but a working proof-of-concept curl command is published in the vendor's GitHub security advisory, and a vendor-released patch is available in version 3.1.3.

Technical ContextAI

Flowise is a self-hosted, open-source LLM workflow orchestration platform exposing a Node.js/Express REST API. The vulnerability is rooted in CWE-862 (Missing Authorization): the Express router at packages/server/src/routes/executions/index.ts correctly wraps the GET handler with checkAnyPermission('executions:view') and the DELETE handler with checkAnyPermission('executions:delete'), but the PUT handler (router.put(['/', '/:id'], executionController.updateExecution)) was shipped without any permission middleware, meaning the RBAC engine is never consulted for update operations. The fix in PR #6409 registers a new RBAC scope executions:update in packages/server/src/enterprise/rbac/Permissions.ts and adds checkAnyPermission('executions:update') to the route, consistent with the platform's existing permission model. Affected CPE: cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:* covering all versions through 3.1.2.

RemediationAI

Upgrade Flowise to version 3.1.3 or later, which introduces the executions:update RBAC permission scope and gates the PUT /api/v1/executions/:id endpoint behind checkAnyPermission('executions:update'). The patched release is available at https://github.com/FlowiseAI/Flowise/releases/tag/flowise@3.1.3, with the underlying code change confirmed in commit 96a9b23b5a103b362a0ee1368d04636755be1bed (PR #6409). If immediate upgrade is not feasible, add a network-layer or API gateway rule to block or require elevated re-authentication for HTTP PUT requests to the /api/v1/executions/* path - note this will disable the Share execution feature for all users until the rule is removed. After patching, audit execution records for unexpected state transitions or data modifications (e.g., executions marked FINISHED that should be FAILED, or anomalous data payloads) to identify potential prior exploitation.