Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, `DELETE /api/v1/chatflows/:id` authorized requests with checkAnyPermission('chatflows:delete,agentflows:delete'), so possession of either permission was sufficient to reach the delete path. The delete logic then resolved the target record only by id and workspaceId and did not validate the target resource type, allowing a caller with only agentflows:delete to delete a CHATFLOW and a caller with only chatflows:delete to delete an AGENTFLOW in the same workspace. This issue is fixed in version 3.1.3.
References
| Link | Resource |
|---|---|
| https://github.com/FlowiseAI/Flowise/commit/2f528ceced74afaa95fc7a282965e7788796448b | Patch |
| https://github.com/FlowiseAI/Flowise/pull/6445 | Issue Tracking Patch |
| https://github.com/FlowiseAI/Flowise/releases/tag/flowise@3.1.3 | Patch Release Notes |
| https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-p5w8-m249-4r4v | Exploit Vendor Advisory |
| https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-p5w8-m249-4r4v | Exploit Vendor Advisory |
Configurations
History
No history.
Information
Published : 2026-08-04 17:17
Updated : 2026-09-14 19:41
NVD link : CVE-2026-69262
Mitre link : CVE-2026-69262
CVE.ORG link : CVE-2026-69262
JSON object : View
Products Affected
flowiseai
- flowise
CWE
CWE-863
Incorrect Authorization
