CVE-2026-69262
Medium
Elevated severity or exploit probability.
CVSS base
8.1
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS — probability of exploitation (30 days)
0.3%
24.8th percentile
CISA KEV
Not listed
Weakness / dates
CWE-863
Published 2026-08-04 · modified 2026-09-14
CVSS breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
| Attack Vector | N | Network |
| Attack Complexity | L | Low |
| Privileges Required | L | Low |
| User Interaction | N | None |
| Scope | U | Unchanged |
| Confidentiality | N | None |
| Integrity | H | High |
| Availability | H | High |
Timeline
- 2026-08-04 — Published (NVD)
- 2026-09-14 — Last modified (NVD)
Description
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.
Affected
References
- https://github.com/FlowiseAI/Flowise/commit/2f528ceced74afaa95fc7a282965e7788796448b
- https://github.com/FlowiseAI/Flowise/pull/6445
- https://github.com/FlowiseAI/Flowise/releases/tag/flowise@3.1.3
- exploit https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-p5w8-m249-4r4v
- exploit https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-p5w8-m249-4r4v