Authenticated execution tampering via missing permission check
Published Aug 4, 2026 · Updated Aug 4, 2026
Missing authorization in Flowise 3.1.2 and earlier allows remote authenticated users to alter execution records through the update API. The PUT /api/v1/executions/:id route calls updateExecution without the checkAnyPermission('executions:update') middleware used by protected execution routes. Any valid account or API key can therefore change state, data, and metadata for any execution in its workspace, corrupting workflow results without broader execution permissions.
Summary
What happened
Missing authorization in Flowise 3.1.2 and earlier allows remote authenticated users to alter execution records through the update API. The PUT /api/v1/executions/:id route calls updateExecution without the checkAnyPermission('executions:update') middleware used by protected execution routes. Any valid account or API key can therefore change state, data, and metadata for any execution in its workspace, corrupting workflow results without broader execution permissions.
The record
- CVE
- CVE-2026-70475
- Published
- Aug 4, 2026
- Updated
- Aug 4, 2026
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- CWE-862, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 4, 2026CVE publishedPublication date reported by the CVE source.
- Aug 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.1.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Execution update authorization-bypass HTTP requestproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo