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. EPSS exploitation probability: 0.3%.

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: 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.

| CVE-2026-70475 HIGH

Missing Authorization (CWE-862)

2026-08-04 GitHub_M

GHSA-fm2f-4339-4p2f

Authentication Bypass Privilege Escalation Flowise Flowiseai

7.1

CVSS 4.0 · Vendor: GitHub_M

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Obtain any valid Flowise API key (any role)
Delivery

Enumerate target execution IDs via GET /api/v1/executions
Exploit

Craft PUT request to /api/v1/executions/:id with manipulated payload
Execution

Server skips RBAC check (no middleware)
Persist

Overwrite execution state and data
Impact

Corrupt workflow audit trail or inject false results

Vulnerability Assessment

Weakness	CWE CWE-862 OWASP Top 10:2025 A01:2025 - Broken Access Control ASVS 5.0 V8 - Authorization Authorization checks on every request MITRE ATT&CK 1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	Exploitation requires a valid authenticated Flowise account or API key with any permission level - the CVSS PR:L metric confirms unauthenticated access is not sufficient. The attacker must be a member of the workspace containing the target execution records, as Flowise workspace isolation limits cross-workspace access. No special configuration, non-default feature flag, or specific deployment mode is required - the vulnerable PUT endpoint is present in every Flowise server deployment running versions 3.1.2 and earlier regardless of how RBAC roles are configured, because the middleware is entirely absent and never evaluated. Exploitation is bounded by: (1) requiring at least one valid user credential or API key, (2) workspace membership scope limiting which execution records are reachable, and (3) impact limited to integrity of execution records with no direct confidentiality or availability consequence per CVSS VC:N/VA:N.
Impact	The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N) correctly characterizes this as a low-complexity, network-accessible attack requiring only a valid authenticated account, with high integrity impact and no confidentiality or availability consequence. Real-world risk is meaningfully elevated in multi-user Flowise deployments: the attack surface is every authenticated user in a workspace, the PoC is a single curl command published in the public advisory, and manipulation of LLM execution records can corrupt audit trails or inject false results into downstream AI pipelines. Single-user or private deployments face substantially lower risk since the prerequisite of a malicious insider or compromised account narrows the realistic attacker pool. No EPSS score was provided in the input data, and the vulnerability is absent from CISA KEV, so no confirmed mass or targeted exploitation is indicated. There is no conflict between data sources; CVSS PR:L correctly reflects that unauthenticated exploitation is not possible.
Exploit ScenarioDerived	A read-only analyst user in a multi-tenant Flowise workspace uses their legitimate API key - issued for view-only dashboard access - to enumerate execution IDs via the authorized GET /api/v1/executions endpoint, then sends a PUT request to /api/v1/executions/<target_id> with a JSON body setting state to FINISHED and injecting arbitrary data, successfully overwriting a peer's execution record without any RBAC check being performed. A working single-command PoC for this scenario is published verbatim in security advisory GHSA-fm2f-4339-4p2f.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 04, 2026

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.

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.

Affected VersionsENISA

Flowise < 3.1.2

Affected Packages

npm flowise fix: 3.1.2, 3.1.3

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

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.

Know when Flowise gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

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

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

Attack Requirements

None

Privileges Required

Low

User Interaction

None

Vulnerable system: Confidentiality

None

Vulnerable system: Integrity

High

Vulnerable system: Availability

None

Subsequent system: Confidentiality

None

Subsequent system: Integrity

None

Subsequent system: Availability

None

Lifecycle Timeline

Patch available

Aug 04, 2026 - 20:01 EUVD

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.

Executive ViewAI

Why It Matters

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 execution records for any workflow. This creates a data integrity and compliance risk, as internal users can undetectably alter business-critical execution data.

Business Impact: High

Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score

0.3%

Top 78% exploitable

Prevalence

Medium

growing open-source LLM orchestration platform, broad AI builder adoption

Threat Intel

1 sources

Data Quality

7 sources

Confidence: High

EUVD 🇯🇵JVN

NVD

CVE.org

EPSS

Vulnrichment GHSA

GitHub

VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.3%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision

Scheduled

Exploitation

Poc

System Exposure· derived

Open

Automatable

Human Impact

High

Technical Impact

Partial

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +36

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Authentication Bypass CRITICAL

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Privilege Escalation HIGH

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.